A known fix for getting all ASP.Net items available in a WSPBuilder project is to amend the .csproj file with a ProjectTypeGuids element. The same goes for VB.Net but the element that needs to be added is different:
Showing posts with label WSPBuilder. Show all posts
Showing posts with label WSPBuilder. Show all posts
Monday, 10 May 2010
WSPBuilder and VB.Net
Developing a solution for a client which want´s the sourcecode in VB.Net (It took some hours before I stopped using ";" and "{}" ;) ).
A known fix for getting all ASP.Net items available in a WSPBuilder project is to amend the .csproj file with a ProjectTypeGuids element. The same goes for VB.Net but the element that needs to be added is different:
{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}
A known fix for getting all ASP.Net items available in a WSPBuilder project is to amend the .csproj file with a ProjectTypeGuids element. The same goes for VB.Net but the element that needs to be added is different:
Saturday, 26 September 2009
Lifecycle problem with WSPBuilder and EditorPart
I had a problem with the ApplyChanges method in an EditorPart class that was used in a WSPBuilder WebPart class (the default web part that WSPBuilder creates). The CreateChildControls in the WebPart class was triggered before the ApplyChanges method in the EditorPart class. Therefore the web part content was not updated and the page had to be reloaded to show any update to the web part.
In the WebPart class that is created from WSPBuilder the CreateChildControls is triggered from the OnInit method. This has the consequence that the ApplyChanges method in the EditorPart class will be triggered after the CreateChildControls in the WebPart class. My solution was to remove the method call in OnInit and then the ApplyChanges method was firing correctly.
In the WebPart class that is created from WSPBuilder the CreateChildControls is triggered from the OnInit method. This has the consequence that the ApplyChanges method in the EditorPart class will be triggered after the CreateChildControls in the WebPart class. My solution was to remove the method call in OnInit and then the ApplyChanges method was firing correctly.
Thursday, 28 May 2009
WSPBuilder: Unicode characters
Got this error message from WSPBuilder when building a new WSP file:
"The filename of the CAB file must not contain Unicode characters!"
I had some some swedish characters in my projectfolder name. I removed it and updated the SLN file with the new path. Problem solved.
// Henrik
"The filename of the CAB file must not contain Unicode characters!"
I had some some swedish characters in my projectfolder name. I removed it and updated the SLN file with the new path. Problem solved.
// Henrik
Subscribe to:
Posts (Atom)