4

How do I force WSPBuilder (through Visual Studio 2010) to deploy a sattelite .NET 4.0 assembly in the GAC?

  • Did you manage to find a solution to this? Thanks, Claudiu :) – user19911 Oct 3 '13 at 14:20
  • No, I ended up having to reference a 3.5 assembly after all – Tudor Olariu Oct 4 '13 at 9:07
1
  • Find your solution file with extension .wsp
  • Change solution extension to .CAB
  • Now open this file and you will see different files in it but the one you need to deal with is manifest.xml

This is how a manifest.xml file created by WSP Builder looks like,

 <?xml version="1.0"?>
    <!-- Solution created by WSPBuilder. 28/06/2013 09:21:25  -->
    <Solution SolutionId="solutionID" xmlns="http://schemas.microsoft.com/sharepoint/">
      <Assemblies>
        <Assembly Location="abc.edgf.asdas.dll" DeploymentTarget="GlobalAssemblyCache">
          <SafeControls>
            <SafeControl Assembly="abc.edgf.asdas, Version=1.0.0.0, Culture=neutral, PublicKeyToken=ewrushdkfjhsdf" Namespace="whatever your namespace is" TypeName="*" Safe="True" />
          </SafeControls>
        </Assembly>
      </Assemblies>
      <TemplateFiles>
  • This is not a good solution, as I need it to be done automatically in Visual Studio. – Tudor Olariu Jul 12 '13 at 8:29
  • You need to put that in your question then !! anyway just add dll's reference to your project and then change "Copy Local" property of dll to "True" and it will be deployed with solution. – Muhammad Raja Jul 12 '13 at 9:39
  • That's the thing - it will not be deployed since WSP builder will detect that it is an un-managed dll (since it is a 4.0 dll) and therefore will not include it in the wsp – Tudor Olariu Jul 12 '13 at 13:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.