Tag Info

Hot answers tagged

30

WSPBuilder in CKS: Development Tools Edition Extension for VS2010. http://cksdev.codeplex.com/ PS. Must have this extension for SP development.


13

We did a recent migration from 2007 to 2010, medium sized project (Silverlight webparts, 30+ other webparts, wfc, images, js, list defintions, Feature receivers and lot more). We converted all the webparts to Visual WebParts (we determined Farm Solution is ok), including namespace conventions. (Had to recreate webparts in publishing pages though). We also ...


10

I have migrated a solution with more than one feature and some assets deployed to the layouts folder from 2007 to 2010. I was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of ...


10

My team has converted a large SP2007 WSP builder project to SharePoint 2010. A few important things to remember especially if you are upgrading the sharepoint content database as well: When recreating features remember to use the same feature ids. Do not change assembly names, namespaces for things like webparts and eventreceivers and other things that are ...


9

I've built hundreds of solutions and web parts using every tool out there (including rolling my own from scratch). WSP is the best tool IMHO for what I do. It's low friction to get started (get the Visual Studio add-in!) and lets you quickly get a web part/feature up and running instantly. Then you can work your solution and do a one-click deploy in ...


7

WSPBuilder is the choice for me, gives you so much for free when developing and a great integration with Visual Studio. There are a lot of hidden gems in WSPBuilder, that you easily forget, such as great automatic CAS generation. Do read Tobias Zimmergrens post on how to get started with it: ...


6

the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). _vti_bin is a virtual directory mapped to the 12/ISAPI folder, so you can ...


6

See our 4 part series about Porting a SharePoint 2007 WSPBuilder solution to SharePoint 2010.


5

There isn't a 100% straightforward way of migrating WSPBuilder projects to 2010 unfortunately. At the time of writing, it's a little-known fact that WSPs from 2007 cannot be imported to 2010, thus ruling out that approach - see http://msdn.microsoft.com/en-us/library/ee231584(VS.100).aspx. If I needed to be 100% sure about my final output, I'd probably use ...


4

One thing I would add is that if you a beginning, try not to jump straight in using these tools. Try to learn how to create a WSP by hand first. That will give you a far better grasp on how these tools are meant to work and how they help. It will also give you an understanding of what to look for if there is an issue with a WSP created by one of the ...


4

A couple of points to consider here: SharePoint isn't designed to have a single package which captures everything. Like most SharePoint 2007 developers, I'd agree with Wictor that WSPBuilder is the way to go for packaging up custom code assets such as assemblies, 12 hive files etc. - these get packaged up into Features and Solutions (.wsp). However this ...


4

Firstly, if you are using SP2010, and VS2010 - you might want to think about using the in built SharePoint tooling rather than WSPBuilder. Secondly, before you will see the webpart you need to enable the feature containing it at the Web or Site level as it has been scoped. Go to Site features within /_layouts/settings.aspx and ensure that the feature ...


3

the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). I've created a simple commandline tool which generates ...


3

Yes you can use WSPBuilder to package all your stuff. It's a great tool for that. You should leave the site backup out of though and restore that manually. Regarding your error; make sure that you have installed the same features/templates on the target farm where you restore your site.


3

The error you're seeing doesn't appear to be related to the SafeControls entry. If that was the case, you'd see a message saying "Unable to add selected web part(s). A Web Part or Web Form Control on this Page cannot be displayed or imported. The type is not registered as safe." In this case, I think it's other elements in web.config which you are missing - ...


3

A comment from the WSPBuilder site. Nice work! Adding third party DLLs worked great when I deployed AJAX and the AJAX Control Toolkit. I created a feature to do all the web.config changes and used the GAC\Reference folder to include the Control Toolkit DLL. Worked great even with multiple servers in the farm. That was a life saver! So include the dll ...


3

I use WSPBuilder (with the VS 2008 add-in) in combination with a custom project template I can develop a working web part and deploy this into my dev environment in about 2 minutes! For single solution packages with one-one relationship to assemblies (which is most small scale projects) this is fine. Just recently had some issues with a larger project with ...


3

WSPBuilder is my current tool of choice, I think VSeWSS is useful for people starting out to use in a SandPit setup, but once you get into real projects it has limitations and just hides too much away from you. I also still use good old fashioned post build events for speed.


3

This isn't possible. If you only want to activate in one site collection, set it as hidden, and activate via stsadm.


3

Yes, it can be used to create Sandboxed solutions. BUT - you don't get the validations etc that Visual Studio OOB gives you.


3

If your DLL is placed in the bin\debug or bin\release folders of your project (e.g. "Copy Local" equal to true for your DLL Reference), the DLL will automatically be included in your WSP and deploy according to the DeploymentTarget of your local WSPBuilder.exe.config file. If you are sharing the same DLL across multiple projects, it might make more sense ...


3

This is purely opinion and conjecture, so I suggest this be community wiki This opinion is further down entirely to the dynamics of the market you operate in or the customers that you serve, but I have found it far more economical and simpler to freeze continual development in SP2007 and build only for SP2010. Continue to support customers on SP2007 by ...


3

Ok, first are both checkboxes at the bottom marked ("Show processes from all users" and "Show processes in all sessions")? If so, maybe you changed the type of code shown under the "Attach to:" field. I would dig through these three settings. If you still can't find the process after that, try an old fashioned reboot.


3

You need to create the directory structure in your solution for WSPBuilder to package & deploy it correctly. The structure will be something like: 12\TEMPLATE\LAYOUTS\MyProjectName\ Once you've got that, you can create new ASP.NET Web Forms in that folder, and they'll be deployed with the WSP. The URL to access them will be something like ...


2

STSDEV is my option. I've build over 30 SharePoint custom solutions involving event handlers, wf, custom web parts, custom application pages and I'm very pleased with STSDEV. One reason is that everything is transparent, you can see the STSADM commands in output windiw and you can run them later on production server. And yes ..stay away from VSeWSS is the ...


2

Those WSP files are existing files, I don't think you can bring them into another WSP. CodePlex has a WSP for installing AJAX to a SharePoint site. Also, CodePlex has a SharePoint Solution Installer which you can use to automate, via a wizard, the installation of WSP files. HTH


2

Jan has made specific SmartTemplates to deploy user controls in WSP builder: http://www.codeplex.com/smarttemplates


2

The typical pattern used here is to use a timer job to make the changes in the web application root. As you've no doubt noticed, such changes are outside the scope of SharePoint's solution framework. Here's an example of this from Gary Lapointe.



Only top voted, non community-wiki answers of a minimum length are eligible