El TecnoBaúl de Kiquenet

Kiquenet boring stories

Posts Tagged ‘vs2012’

Sharepoint Projects and Crash VS 2012

Posted by kiquenet en 22 julio 2014

I get this error in my Sharepoint 2013 Project when I try Publish it (for generate WSP file)

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: devenv.exe
  Problem Signature 02: 11.0.50727.1
  Problem Signature 03: 5011ecaa
  Problem Signature 04: Microsoft.VisualStudio.SharePoint.Project
  Problem Signature 05: 11.0.60226.0
  Problem Signature 06: 512c2dba
  Problem Signature 07: 18a8
  Problem Signature 08: 1d
  Problem Signature 09: System.NullReferenceException
  OS Version:   6.1.7601.2.1.0.274.10
  Locale ID:    2057
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
  1. Exe File Name
  2. Exe File assembly version number
  3. Exe File Stamp
  4. Exe file full assembly name
  5. Faulting assembly version
  6. Faulting assembly timestamp
  7. Faulting assembly method def
  8. Faulting method IL Offset within the faulting method
  9. Exception type

And also here is a MSDN article on the same.

Finally, I get a solution. In my csproj file, it was dissapeared Package Folder.

Only I do this steps:

  • Edit csproj file
  • Add this nodes (for include Package folder and files)
  • Reload csproj Project
  • Publish again
<None Include="Package\Package.package">
  <PackageId>{1c40a17c-1af5-4fce-b7ed-702badd23db3}</PackageId>
</None>
<None Include="Package\Package.Template.xml">
  <DependentUpon>Package.package</DependentUpon>
</None>

http://www.sharepointstuffs.com/fix-for-visual-studio-2012-crash-on-publish-of-sharepoint-wsp/

Basically you need to make sure that the "site url" is not blank.

http://stackoverflow.com/a/24858405/206730

Posted in .NET, Sharepoint, Soporte | Etiquetado: , , , , , | Leave a Comment »

Create Private Accessors for Visual Studio 2012

Posted by kiquenet en 19 mayo 2014

Con Visual Studio 2012 desaparece la creación desde IDE de los Private Accessors.

Posibles soluciones: crear los Private Accessors con la clase Microsoft.VisualStudio.TestTools.UnitTesting.PrivateObject o usar el comando publicize.exe.

Open a command prompt, or a “VS2013 x86 Native Tools Command Prompt” to have the search path already set up, and run publicize.

In case you do not have the path set up correctly, the tool can be found at
%Program Files (x86)%\Microsoft Visual Studio 11.0\Common7\IDE for Visual Studio 2012 or %Program Files (x86)%\Microsoft Visual Studio 12.0\Common7\IDE for VS 2013.

publicize.exe [options] input-assembly

publicize.exe creates classes named NameOfTheSourceClass_Accessor. In case the class to be tested is called MyClass, the accessor is named MyClass_Accessor.

Starting with Visual Studio 2012, private accessors cannot be created any more by the IDE. The post Home-made Private Accessor for Visual Studio 2012+ presents an approach on how to create private accessors using the classMicrosoft.VisualStudio.TestTools.UnitTesting.PrivateObject.

Axel Mayer noted in the MSDN forums post How to create private accessors in VS 2012 that one can use the command line tool publicize.exe to create private accessors too.

Referencias:
http://blog.instance-factory.com/?p=1036
http://blog.instance-factory.com/?p=810

http://stackoverflow.com/questions/17850406/replacements-for-private-accessors-in-visual-studio-2012

Home-made Private Accessor for Visual Studio 2012+

How to create private accessors in VS 2012

publicize.exe documentation

Posted in .NET, VisualStudio | Etiquetado: , | Leave a Comment »