Tag Info

Hot answers tagged

12

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 ...


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 ...


9

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 ...


9

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 ...


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 ...


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

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

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.


2

One technique I have used is to convert my SharePoint 2007 projects to VSeWSS 1.3 March CTP. The VSeWSS import tool is released]1 and converts your project to a Visual Studio 2010 project targeted at SharePoint 2010. Unlike previous versions of the tool, as of March CTP, VSeWSS addresses most developer needs. Paul Andrew and Kirk Evans provide excellent ...


2

Sounds strange since it should work. Using WSPBuilder you should create your project as follows: Create a new WSP Builder project Add a subfolder to the /12/ folder called Config In the /12/Config folder add a file called stsadmcommands..xml. Make sure that it always starts with stsadmcommands Add a class and inherit from ISPStsadmCommand Implement the ...


2

Not enough information to suggest a solution, but here are a few links -- http://wspbuilder.codeplex.com/workitem/11301 http://wspbuilder.codeplex.com/workitem/13169 http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/294676f0-297e-4df3-b286-d468072e1d18/


2

One of a former project I worked on, I use a custom site template to hide features to other site collections. The idea is to follow these steps : create a custom site template specific to your application. I often use to starts from the blank site definition to start from scratch (but it can depends on your requirements) create all features related to ...


2

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 ...


1

OK, digging around made me realize that I needed to understand how Visual Studio generates the folder name and if it could be tweaked. And, of course, it can. Every feature has a property called Deployment Path. This is set to the replaceable parameter: $SharePoint.Project.FileNameWithoutExtension$_$SharePoint.Feature.FileNameWithoutExtension$ by ...


1

If you got RDP access to the server, I'd do it this way. Open the C:\Windows\assembly folder Open the folder where your dll is located Copy the dll to the assembly folder Wait untill you can reset the webserver Do an iisreset /noforce or recycle the application pools via IIS Manager If you don't have (RDP) access to the server you could write a script ...


1

Like others are saying also, a WSP Builder project can just as easily be added to SourceSafe/TFS as any other project. The steps to do this are: File -> New -> Project Choose a WSPBuilder Project In the Solution Explorer of VS you right-click on the solution (or project, whatever you want). Choose the option Add Solution to Source Control Fill in your ...


1

You can edit the web item templates to the project file itself. To add to *.csproj: <ProjectTypeGuids>...;{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids> To add *.vbproj file: <ProjectTypeGuids>...;{f184b08f-c81c-45f6-a57f-5abd9991f28f}</ProjectTypeGuids> I'm pretty sure that these are the VS08 GUIDs. I don't know if ...


1

I have seen intermittent issues with intellisense as well - here are the key things I have noticed: 1) Sometimes the project/file opens in Visual Studio 2005 - where the intellisense is garbage compared to the 2008/2010 editions. Make sure it is the correct version of visual studio. 2) For the intellisense to work right you need to let it know what ...



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