to SharePoint 2007 hours, in the year last week, I had all desired assemblies in my deployment project reference so that they are copied from the WSPBuilder Extensions when creating the WSP Solution. Or the other way, to build each project a After a build event to copy the compiled assembly to the deployment project - in any case it is either difficult or unpleasant.
dare I am currently taking my first steps with SharePoint 2010 in conjunction with Visual Studio 2010 (the possibilities with SharePoint Designer 2010, Visio 2010, a few ranks are further back on my todo list) and can already say that the developer about the developer some works can be removed. Deployment for a decent one does not need 3rd party tools, that's all right now with Visual Studio.
To return to the title of this paper - also for the integration of assemblies in a WSP Solution, Microsoft has something about what evidence the following screenshots:
- overview of my dummy Solution
- (note the "Advanced" Tab below) Package Designer
- Assembly to add to the package ( Do not forget the assembly to sign for the GAC with a "strong assembly name")
- See, the assemblies appear in fact after the deployment to the GAC on (who knew?)
The other options in the Package designers under the tab "Advanced" I have not looked closely, but certainly include a few useful functions.
0 comments:
Post a Comment