Microsoft.VisualStudio.Package.Project.dll missing in RC1?

Microsoft.VisualStudio.Package.Project.dll missing in RC1?

• CKa

  It seems like we've clarified the main issue here.  Basically MS took out this DLL from the RC build and intended to release it in source code format in the SDK.  But the source didn't make it to the Sept CTP.  Until they either release it separately, or get it into a future CTP (most likely Oct), we will only be able to build our code with the stubbed version, but won't be able to run it in RC1.
  

  
  

• ParkSys

  Sorry my mistake. When I said "Microsoft.VisualStudio.Package.Project" in my replly, I meant  "Microsoft.VisualStudio.Package.LanguageService".
  

• James McKinnon

  I am sure one of the VSSDK team will post a definitive reply, but my understanding is that:
  
  Assemblies shipping with the VSSDK contain no code and are to be found by default in C:\Program Files\Visual Studio 2005 SDK\2005-10\VisualStudioIntegration\Common\Assemblies
  
  These are for use at Build time, and get picked up by the VS IDE references dialog.
  At run-time the assemblies in the GAC are used, and these typically ship with VS 2005 itself (not the SDK). For example, Microsoft.VisualStudio.Package.Project is actually used by the Xml editor in the product.
  
  By stubbing out the code from the VSSDK assemblies, it will be very obvious if you accidentally end up calling the wrong one at runtime.
  
  There have been problems recently where the VSSDK assemblies (and IDL) don't match the assemblies installed by VS itself, but as far as I'm aware, this has now been tidied up and the VSSDK September CTP assemblies are spot on with the RC1 build.
  
  If Microsoft.VisualStudio.Package.Project is missing from the GAC on your machine, I think this a bad install of Visual Studio.
  
  

• neuling700

  Package.Project.dll no longer ships with VS2005. Instead, it will be available in source code form only, in the SDK. The idea is that you can include the sources in directly in your projects. Because it lacks source-code control support, the team decided to pull it from VS so it can be improved independently of the platform.
  
  

• TroyMac

  I have also run across the same issue.< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

  This will only work for the purpose of building and registering your package if you are using the Microsoft.VisualStudio.Package.Project.dll that is located in the

  …\Visual Studio 2005 SDK\2005-09\VisualStudioIntegration\Common\Assemblies

   directory that is dated

   

  08/02/2005  10:12 AM            57,344 Microsoft.VisualStudio.Package.Project.dll

   

  If you use ildasm on it you will see that it is a stubbed out version that has no implementation so you will not be able to run with it.

   

  for example

   

  .method public hidebysig specialname rtspecialname

          instance void  .ctor(... ) cil managed

  {

    // Code size       1 (0x1)

    .maxstack  8

    IL_0000:  ret

  } // end of method FileNode::.ctor

   
  Mark

  
  

• Rajavanya

  Ah, I see.  I think you're right about the C:\Program Files\Visual Studio 2005 SDK\2005-10\VisualStudioIntegration\Common\Assemblies
   vs. what's in the GAC.  This is very helpful, as I can take the assemblies in the GAC and still disassemble them.
  
  I don't have Microsoft.VisualStudio.Package.Project in the GAC, but as I understand it this is intentional, as MS plans to release this in source code only format.  I guess they missed doing this for the Sept CTP.
  

• Paolo Pialorsi

  Not sure if it will help, but we had a similar problem and while we're still working through the bugs, to get past the immediate problem you're having, we registered the project assembly in the GAC.  Try running the following at the command line in your envsdk\common\VSIA folder, or wherever the project .dll is:
  
  Sn –Vr Microsoft.VisualStudio.Package.Project.dll
  Gacutil /f /i Microsoft.VisualStudio.Package.Project.dll
  
  use at your own risk
  

• unionize

  Yes, we noticed the same thing.  I initially thought the implementation was stubbed out too, but I'm beginning to think otherwise.  The reason I say this is two-fold.  First, the file size is pretty large for being stubbed out.  It is larger than that of Beta 2. 
  
  Second, you'll notice that pretty much all of the shell assemblies don't respond to disassembly; try use ildasm on a more fundamental assembly like Microsoft.VisualStudio.Shell.dll.  This one also appears stubbed out.  But, it is used by the ToolWindow sample and this works fine.  Plus, we used an older version of the MPF project system code (in source code format) and got further along than using the Microsoft.VisualStudio.Package.Project.dll that comes with the Sept SDK.  The older MPF project system code still relies on the Microsoft.VisualStudio.Shell.dll, so this tells me it's not just stub code.
  

• D-Rain

  I see.  Releasing the source as part of the SDK would be very helpfull.  Do you have any info on when this will be available
  
  I'm assuming until the source is released in the SDK, I will have to use the binary that is in the Sept CTP SDK then   However, I still can't get my package to register due to the errors I'm getting in my previous post.  As I said, the samples as well as new VS Package projects created via the wizard all work fine.
  
  Do you have any suggestions
  
  Thanks very much.
  
  Eric
  

• ljCharlie

  After tweaking my VSPackage project in RC1 for awhile, I was able to build everything, but I'm getting the following error from RegPkg:

  regpkg : error : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

  Could not load file or assembly 'Microsoft.VisualStudio.Package.Project, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

  Could not load file or assembly 'Microsoft.VisualStudio.Package.Project, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

  Could not load file or assembly 'Microsoft.VisualStudio.Package.Project, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

  Could not load file or assembly 'Microsoft.VisualStudio.Package.Project, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

  Could not load file or assembly 'Microsoft.VisualStudio.Package.Project, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

  But I'm able to build the VSIP samples as well as create new VS Package project via the wizard just fine.

  Any help would be great!

  Thanks

  Eric
  

  
  

• mediterian

  Exactly.
  

  
  
• Microsoft.VisualStudio.Package.Project.dll missing in RC1?