STSDEV: Simple Tools for SharePoint 2007 Development

Closed Issue: For application pages solution. When first using debugbuild, debugdeploy no longer works [856]

bphillips76 — Thu, 16 May 2013 06:42:09 GMT

When first building with debugbuild, debugdeploy no longer works. Masterpage can no longer be found.

Closed Issue: Empty node in manifest.xml [2571]

wlyq — Thu, 16 May 2013 06:42:08 GMT

If there are no template files then an empty <TemplateFiles /> node is created in manifest.xml. This fails validation when calling addsolution.

Closed Issue: Assembly locations in solution manifest should use root directory [2803]

bphillips76 — Thu, 16 May 2013 06:42:08 GMT

When adding an external assembly to a solution using SolutionConfig.xml, the entry looks like this:
<Assembly DeploymentTarget="GlobalAssemblyCache" Location="..\..\..\lib\log4net.dll" />

The Location attribute is added as-is to the solution manifest:
<Assembly Location="..\..\..\lib\log4net.dll" DeploymentTarget="GlobalAssemblyCache" />

However, solution files are added at the root level of the solution file, not in a path structure. The Location should look like this:
<Assembly Location="log4net.dll" DeploymentTarget="GlobalAssemblyCache" />

Closed Issue: Stsdev 1.3 FileNotFound exception [2822]

bphillips76 — Thu, 16 May 2013 06:42:07 GMT

This may be similar to the other error posted.

When I try and create a new 'Empty Solution (C# Assembly)' I am getting a FileNotFound exeption "Could not find file 'abc'" where abc is the name of the project it was trynig to create.

It works fine when I create an 'Empty Soltuon (No Assembly) - but of course that it not the option I would like to use :)

Does anyone have a workaround for this as it kind of prevents one from using the tool.

Closed Issue: Creating new Sequential Template Solution VS2008 .NET 3.0 throws error on build. [3129]

bphillips76 — Thu, 16 May 2013 06:42:07 GMT

When I use STSDEV to create VS 2008 .NET 3.0 Sequential Workflow Solution it throws an error when I first try and build it.

The error is well documented here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3865469&SiteID=1

Basically the .csproj file needs to have the a line changed:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets" />
to
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" />

This seems to fix the problem and "has no side affects".

I am using VS 2008 SP1, .NET 3.5 SP1.

For now I'm manually changing this after the wizard creates it.

(great work on this product guys!)

Closed Issue: STSDEV created VS project doesn't compile due to file references [3138]

bphillips76 — Thu, 16 May 2013 06:42:07 GMT

I created a STSDEV Workflow Project and built the solution no problems. But when I try and add the project to another Solution it throws an exception:

Message:
{"Could not find a part of the path 'C:\\Source\\Development\\Barminco\\DSCIT.BAR.CapExRequest\\DeploymentFiles\\SolutionConfig.xml'."}

StackTrace:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter.CreateFile(String path, Boolean append)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path)
at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget, PermissionSet CasPermissions)
at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget)
at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings)
at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment)
at stsdev.SolutionBuilder.LoadSolutionConfigFile()
at stsdev.SolutionBuilder.RefreshDeploymentFiles()
at stsdev.SolutionBuilder.RefreshDeploymentFiles(String TargetSolutionName, String TargetSolutionDirectory)
at stsdev.Program.Main(String[] args)

I'm assuming this means that there are some ties to the Solution file that is built. Is it possible to remove this dependency? or document a way of making another Solution file work with this project.

Closed Issue: lastest code files miss essential pieces from 1.3 release [3787]

bphillips76 — Thu, 16 May 2013 06:42:06 GMT

If you download the code from nov 2008, you run into a lot of issues, you don't run into, when you build from latest release build files. The reason i use the november files is, there a certain fixes regarding problems with created signed key files that occur in the latest official release (may 2008) code.
An example: FeatureManifests are built in the last one, regardless, if a feature folder exists or not and if it exists, it only adds feature.xml instead of all features. In the may 2008 version this worked just fine. My question is: did something go wrong with file merges in tfs after the 1.3 release from may 2008 or are there new features in stsDev that introduce build errors and stsadm deployment errors?

Closed Issue: Large WSP File Size [4102]

bphillips76 — Thu, 16 May 2013 06:42:05 GMT

If the file size of the WSP is too big then STSDEV won't package everything up into the WSP file. See this blog for more info:

http://blogs.pointbridge.com/Blogs/monnette_jeff/Pages/Post.aspx?_ID=8

Closed Issue: Public Key Token Intermittently Not Generated Correctly for Feature Receiver on Project Creation [4751]

bphillips76 — Thu, 16 May 2013 06:42:05 GMT

I've had two cases where the public key token for the feature receiver in feature.xml file is not generated correctly. The first time I was getting an error upon solution deployment that it couldn't load the feature receiver class and after looking at for a while I couldn't figure out why. In that case I wasn't using the FeatureReceiver so I just commented it out of feature.xml and went on my merry way.

But I had the same problem today for a new feature and finally figured out that the public key token was incorrect by comparing it to my assembly in the GAC. In this case it was missing the 5th character in the token. All the other characters were correct - it was just missing the 5th character.

I realize this will probably be difficult to debug as it seems to be intermittent, but wanted to post it here in case anyone else gets the problem in the future they can add to this thread.

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

New Post: How can I using existing DeploymentFiles

jirawat — Sat, 18 Feb 2012 03:15:55 GMT

I need to modify the old project from other person. In the VS solution explorer it contains DeploymentFiles folder. This project use signing key with .pfx file.

How can I using existing .ddf and manifest.xml files?

Thank for advance

New Post: STADM always reverts to the Program Files (x86) Path

jamierjb — Fri, 17 Feb 2012 18:11:21 GMT

I just recently ran into the same problem. I had to hard code in "C:\Program Files\" instead of using the "$(ProgramFiles)" variable. Once I did that, and closed and reopened VS, it worked for me.

edit: I'm using stsdev 1.4

New Post: Debugging Issue

rasor — Thu, 17 Nov 2011 17:06:14 GMT

As for 2:

This is shorter:

del $(ProjectDir)$(TargetName).XmlSerializers.dll

Checkout this nice post, too: http://hashtagfail.com/post/5255977780/sgen-loaderexceptions-error

Reviewed: STSDEV 1.4 (Apr 13, 2011)

nguyensinhnguyen — Wed, 13 Apr 2011 08:17:24 GMT

Rated 4 Stars (out of 5) - great tools for developing on Sharepoint

New Post: Deploying an stsadm extension with STSDEV

mags — Sun, 20 Feb 2011 03:55:46 GMT

I was not able to get it to work with STSDEV so I just setup my own build script etc.

New Post: Deploying an stsadm extension with STSDEV

conaner — Fri, 18 Feb 2011 22:55:32 GMT

Did you ever find an answer? I have the same problem

Reviewed: STSDEV 1.4 (Feb 11, 2011)

JeepGuy — Fri, 11 Feb 2011 23:47:38 GMT

Rated 1 Stars (out of 5) - This doesn't work in Sever 2008 with Visual Studio 2008... what silliness... Do it by hand stop the madness... The videos are a joke.

New Post: STSDVE for Sharepoint 2010

alrama — Mon, 07 Feb 2011 16:44:57 GMT

I suppose that this is a dead project despite I consider STSDEV a better tool of WSPBuilder or Visual Studio 2010 Sharepoint Tools.

New Post: How to Create setup file using STSDEV Tool?

anilraparla03 — Thu, 03 Feb 2011 11:11:05 GMT

Hi,

How to Create setup.exe file using stsdev tool for Sharepoint 2007 application.

Regards

Anil.R