Reputation: 476
I am trying to deploy my first custom aspx page in sharepoint:
I am following this detailed howto:
http://geeksconnected.com/jamil/Lists/Posts/Post.aspx?ID=19
Unfortunately, it quickly becomes incomplete toward the bottom. I am running into two issues thus far:
How do you grant the VSeWSS Administrator privileges so that the "Deploy" option will work in Visual Studio?
It cuts off half of the <SafeControl>
tag in the example, and I am not sure what to put after the PublicKeyToken=
option. All current attempts completely break sharepoint.
Any solutions and explanations would be appreciated. Thanks in advance for any help.
Upvotes: 1
Views: 4865
Reputation: 2849
Did you follow the instructions for post-install configuration of VSeWSS 1.3? http://blogs.msdn.com/steve_fox/archive/2009/03/18/vsewss-1-3-post-install-configuration.aspx
Upvotes: 2
Reputation: 2172
Do yourself a favor and use WSPBuilder and its companion SPVisualDev instead of VSeWSS. Both of these tools are on CodePlex.com
They will take care of your safecontrols problem by adding that into the WSP file that any SharePoint administrator can install. (Frankly, modifying web.config by hand in a SharePoint environment is a big no-no in my mind, especially safecontrols)
They will also not need the elaborate 2-project spoof just to have a codebehind for an ASPX page that the article you quoted promotes. SPVisualDev will give you the option to do 'add new item' in visual studio and select a new Page or UserControl with codebehind, and take care of the deployment through WSP. Easy as!
Upvotes: 2
Reputation: 1408
2.The safe control tag should look like the following:
<SafeControl Assembly="[Assembly Name]" Namespace="[Namespace]" TypeName="*" Safe="True" />
To get the public key token you first have to sign the assembly (properties on the project->signing). Then you can build it and drop in the GAC (C:\Windows\assembly) and read the public key token directly in your explorer window.
Upvotes: 0