VSeWSS error - the response message does not match the content type
I got the following error trying to build a project of the WSS extensions for Visual Studio 1.3
You can fix it by: Add / Remove Programs and add HTTP Activation. Here's the step by step: Use Turn Windows Features On and Off in the control panel, then locate .NET Framework 3.5 and then find Windows Communication Foundation HTTP Activation. Select it and choose.
WSS Extensions 1.3 for Visual Studio 2008 CTP
On the Microsoft SharePoint Team Blog you can read about the CTP release of version 1.3 of Windows Sharepoint Services 3.0 extenisions for Visual Studio 2008 (VSeWSS).
The new features in VSeWSS 1.3 are:
· Can be installed on x64 Server OS machines running SharePoint x64. Previously only x86 Server OS could be used.
· Separate build commands for package, deploy and retract are added
· Command line build, package and retract commands are included enabling continuous integration and build servers. Previously command line build of SharePoint projects was very difficult
· Refactoring support for renaming of Web Parts. Previously renaming a web part required changes in several files in the project
· WSP View improvements for consistency of deleting feature elements, merging features and adding event receivers to features
· Solution Generator can now generate solutions from publishing sites. Previously only regular sites could be generated
· Allowing partial trust BIN deployments of web parts. CAS configuration must still be provided by the developer.
· New project item template for SharePoint RootFiles items
· Deployment will now optionally remove conflicting existing features on the development server prior to redeployment. Previously any feature name conflicts would result in an error
· Ancillary assemblies such as for business logic can now be added to the SharePoint Solution WSP
· Hidden features related to Site Definition projects are now shown in WSP View. They are no longer hidden
· For advanced users a fast deploy is included to update only the compiled assembly on the SharePoint development installation
· The User Guide is now installed with the extensions instead of being a separate download
The final release of VSeWSS 1.3 is planned for the North American Spring of 2009.
Download now!
Problems using WSS Extensions for Visual Studio
ERROR: “This solution contains two assemblies with the same name, or the SharePoint server already has an assembly with the specified name.” when deploying a solution using the Visual Studio Extensions for SharePoint (VSEWSS) after you have already deployed it to a different site on the same server.
Resolution:
- Remove the solution’s assembly from the Global Assembly Cache (GAC).
- Gacutil –uf assemblyName (note: no .dll extension is specified)
- Rename or Remove the feature from “Program Files\Common Files\Microsoft Shared\
web server extensions\TEMPLATE\FEATURES\FeatureName”
//FeatureName may not be the same as assembly name –
look in your manifest.xml to find the correct name
[/code]
ERROR: When trying to deploy a VSEWSS solution using the Visual Studio “Deploy” command you receive the error “Value does not fall within the expected range.”
Resolution:
Remove all projects except the VSEWSS project from the Visual Studio solution
then attempt your deployment again.
ERROR: Value does not fall within the expected range (Line 0, Column 0)
Resolution:
- Delete the pkg folder in your solution foler.
- Start building and deploying again.
Read More on MSDN Forum
Unable to add selected Web Part - Incompatible Web Part markup detected
During developing a custom toolpart using WSS extensions for Visual Studio 2005
I got the following error by adding my webpart to the webpart page:
"Incompatible Web Part markup detected. Use *.dwp web part XML instead of
*.webpart web part xml". By overriding the GetToolParts() method we have to
derive or Web Part class from the Microsoft.SharePoint.WebPartPages.WebPart
class. A Web Part derived from this class expects a .dwp file. But the
solutionpackage (.wsp) created by the WSS Extensions creates a .webpart-file. We
can simply solve this error by making a custom .dwp file:
<?xml version="1.0"?>
<WebPart xmlns="http://schemas.microsoft.com/WebPart/v2">
<Assembly>AssemblyName(with no .dll extension),
Version=VersionNumber, Culture=Culture,
PublicKeyToken=PublicKeyToken</Assembly>
<TypeName>WebPartNamespace.WebPartClassName</TypeName>
<Title>DefaultWebPartTitle</Title>
<Description>WebPartDescription</Description>
</WebPart>
Delete your .webpart file from you Feature directory in the 12-hyve and place here your new .dwp file. Go to Site Settings --> Web Parts (= Web Part Gallery) and delete your Web Part (which currently reffers to a .webpart file). Upload your new .dwp file. Now you can add your Web Part to your Web Part page!