stsdev Work Item Rss Feed

stsdev Work Item Rss Feedhttp://www.codeplex.com/stsdev/WorkItem/List.aspxstsdev Work Item Rss DescriptionReopened Issue: For application pages solution. When first using debugbuild, debugdeploy no longer works [856]http://stsdev.codeplex.com/workitem/856When first building with debugbuild, debugdeploy no longer works. Masterpage can no longer be found.<br />bphillips76Fri, 14 Jun 2013 08:02:09 GMTReopened Issue: For application pages solution. When first using debugbuild, debugdeploy no longer works [856] 20130614080209AReopened Issue: Empty <TemplateFiles /> node in manifest.xml [2571]http://stsdev.codeplex.com/workitem/2571If there are no template files then an empty <TemplateFiles /> node is created in manifest.xml. This fails validation when calling addsolution.<br />wlyqFri, 14 Jun 2013 08:02:08 GMTReopened Issue: Empty <TemplateFiles /> node in manifest.xml [2571] 20130614080208AReopened Issue: Assembly locations in solution manifest should use root directory [2803]http://stsdev.codeplex.com/workitem/2803When adding an external assembly to a solution using SolutionConfig.xml, the entry looks like this:<br /> <Assembly DeploymentTarget="GlobalAssemblyCache" Location="..\..\..\lib\log4net.dll" /><br /> <br />The Location attribute is added as-is to the solution manifest:<br /> <Assembly Location="..\..\..\lib\log4net.dll" DeploymentTarget="GlobalAssemblyCache" /><br /> <br />However, solution files are added at the root level of the solution file, not in a path structure. The Location should look like this:<br /> <Assembly Location="log4net.dll" DeploymentTarget="GlobalAssemblyCache" /><br />bphillips76Fri, 14 Jun 2013 08:02:08 GMTReopened Issue: Assembly locations in solution manifest should use root directory [2803] 20130614080208AReopened Issue: Stsdev 1.3 FileNotFound exception [2822]http://stsdev.codeplex.com/workitem/2822This may be similar to the other error posted.<br /> <br />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.<br /> <br />It works fine when I create an 'Empty Soltuon (No Assembly) - but of course that it not the option I would like to use :)<br /> <br />Does anyone have a workaround for this as it kind of prevents one from using the tool.<br />bphillips76Fri, 14 Jun 2013 08:02:08 GMTReopened Issue: Stsdev 1.3 FileNotFound exception [2822] 20130614080208AReopened Issue: Creating new Sequential Template Solution VS2008 .NET 3.0 throws error on build. [3129]http://stsdev.codeplex.com/workitem/3129When I use STSDEV to create VS 2008 .NET 3.0 Sequential Workflow Solution it throws an error when I first try and build it.<br /> <br />The error is well documented here:<br />http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3865469&SiteID=1<br /> <br />Basically the .csproj file needs to have the a line changed:<br /> <Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets" /><br />to<br /> <Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" /><br /> <br />This seems to fix the problem and "has no side affects". <br /> <br />I am using VS 2008 SP1, .NET 3.5 SP1.<br /> <br />For now I'm manually changing this after the wizard creates it.<br /> <br />(great work on this product guys!)<br />bphillips76Fri, 14 Jun 2013 08:02:08 GMTReopened Issue: Creating new Sequential Template Solution VS2008 .NET 3.0 throws error on build. [3129] 20130614080208AReopened Issue: STSDEV created VS project doesn't compile due to file references [3138]http://stsdev.codeplex.com/workitem/3138I 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:<br /> <br />Message:<br />{"Could not find a part of the path 'C:\\Source\\Development\\Barminco\\DSCIT.BAR.CapExRequest\\DeploymentFiles\\SolutionConfig.xml'."}<br /> <br />StackTrace:<br /> at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)<br /> 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)<br /> at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)<br /> at System.IO.StreamWriter.CreateFile(String path, Boolean append)<br /> at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)<br /> at System.IO.StreamWriter..ctor(String path)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget, PermissionSet CasPermissions)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment)<br /> at stsdev.SolutionBuilder.LoadSolutionConfigFile()<br /> at stsdev.SolutionBuilder.RefreshDeploymentFiles()<br /> at stsdev.SolutionBuilder.RefreshDeploymentFiles(String TargetSolutionName, String TargetSolutionDirectory)<br /> at stsdev.Program.Main(String[] args)<br /> <br />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.<br />bphillips76Fri, 14 Jun 2013 08:02:08 GMTReopened Issue: STSDEV created VS project doesn't compile due to file references [3138] 20130614080208AReopened Issue: lastest code files miss essential pieces from 1.3 release [3787]http://stsdev.codeplex.com/workitem/3787If 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.<br />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?<br />bphillips76Fri, 14 Jun 2013 08:02:08 GMTReopened Issue: lastest code files miss essential pieces from 1.3 release [3787] 20130614080208AReopened Issue: Large WSP File Size [4102]http://stsdev.codeplex.com/workitem/4102If 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:<br /> <br />http://blogs.pointbridge.com/Blogs/monnette_jeff/Pages/Post.aspx?_ID=8<br />bphillips76Fri, 14 Jun 2013 08:02:07 GMTReopened Issue: Large WSP File Size [4102] 20130614080207AReopened Issue: Public Key Token Intermittently Not Generated Correctly for Feature Receiver on Project Creation [4751]http://stsdev.codeplex.com/workitem/4751I'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. <br /> <br />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.<br /> <br />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.<br />bphillips76Fri, 14 Jun 2013 08:02:07 GMTReopened Issue: Public Key Token Intermittently Not Generated Correctly for Feature Receiver on Project Creation [4751] 20130614080207AClosed Issue: For application pages solution. When first using debugbuild, debugdeploy no longer works [856]http://stsdev.codeplex.com/workitem/856When first building with debugbuild, debugdeploy no longer works. Masterpage can no longer be found.<br />bphillips76Thu, 16 May 2013 06:42:09 GMTClosed Issue: For application pages solution. When first using debugbuild, debugdeploy no longer works [856] 20130516064209AClosed Issue: Empty <TemplateFiles /> node in manifest.xml [2571]http://stsdev.codeplex.com/workitem/2571If there are no template files then an empty <TemplateFiles /> node is created in manifest.xml. This fails validation when calling addsolution.<br />wlyqThu, 16 May 2013 06:42:08 GMTClosed Issue: Empty <TemplateFiles /> node in manifest.xml [2571] 20130516064208AClosed Issue: Assembly locations in solution manifest should use root directory [2803]http://stsdev.codeplex.com/workitem/2803When adding an external assembly to a solution using SolutionConfig.xml, the entry looks like this:<br /> <Assembly DeploymentTarget="GlobalAssemblyCache" Location="..\..\..\lib\log4net.dll" /><br /> <br />The Location attribute is added as-is to the solution manifest:<br /> <Assembly Location="..\..\..\lib\log4net.dll" DeploymentTarget="GlobalAssemblyCache" /><br /> <br />However, solution files are added at the root level of the solution file, not in a path structure. The Location should look like this:<br /> <Assembly Location="log4net.dll" DeploymentTarget="GlobalAssemblyCache" /><br />bphillips76Thu, 16 May 2013 06:42:08 GMTClosed Issue: Assembly locations in solution manifest should use root directory [2803] 20130516064208AClosed Issue: Stsdev 1.3 FileNotFound exception [2822]http://stsdev.codeplex.com/workitem/2822This may be similar to the other error posted.<br /> <br />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.<br /> <br />It works fine when I create an 'Empty Soltuon (No Assembly) - but of course that it not the option I would like to use :)<br /> <br />Does anyone have a workaround for this as it kind of prevents one from using the tool.<br />bphillips76Thu, 16 May 2013 06:42:07 GMTClosed Issue: Stsdev 1.3 FileNotFound exception [2822] 20130516064207AClosed Issue: Creating new Sequential Template Solution VS2008 .NET 3.0 throws error on build. [3129]http://stsdev.codeplex.com/workitem/3129When I use STSDEV to create VS 2008 .NET 3.0 Sequential Workflow Solution it throws an error when I first try and build it.<br /> <br />The error is well documented here:<br />http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3865469&SiteID=1<br /> <br />Basically the .csproj file needs to have the a line changed:<br /> <Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.0\Workflow.Targets" /><br />to<br /> <Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" /><br /> <br />This seems to fix the problem and "has no side affects". <br /> <br />I am using VS 2008 SP1, .NET 3.5 SP1.<br /> <br />For now I'm manually changing this after the wizard creates it.<br /> <br />(great work on this product guys!)<br />bphillips76Thu, 16 May 2013 06:42:07 GMTClosed Issue: Creating new Sequential Template Solution VS2008 .NET 3.0 throws error on build. [3129] 20130516064207AClosed Issue: STSDEV created VS project doesn't compile due to file references [3138]http://stsdev.codeplex.com/workitem/3138I 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:<br /> <br />Message:<br />{"Could not find a part of the path 'C:\\Source\\Development\\Barminco\\DSCIT.BAR.CapExRequest\\DeploymentFiles\\SolutionConfig.xml'."}<br /> <br />StackTrace:<br /> at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)<br /> 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)<br /> at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)<br /> at System.IO.StreamWriter.CreateFile(String path, Boolean append)<br /> at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)<br /> at System.IO.StreamWriter..ctor(String path)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget, PermissionSet CasPermissions)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings, AssemblyDeploymentTarget DeploymentTarget)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment, Boolean SafeControlSettings)<br /> at stsdev.SolutionConfigBuilder.Create(String FilePath, Boolean AssemblyDeployment)<br /> at stsdev.SolutionBuilder.LoadSolutionConfigFile()<br /> at stsdev.SolutionBuilder.RefreshDeploymentFiles()<br /> at stsdev.SolutionBuilder.RefreshDeploymentFiles(String TargetSolutionName, String TargetSolutionDirectory)<br /> at stsdev.Program.Main(String[] args)<br /> <br />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.<br />bphillips76Thu, 16 May 2013 06:42:07 GMTClosed Issue: STSDEV created VS project doesn't compile due to file references [3138] 20130516064207AClosed Issue: lastest code files miss essential pieces from 1.3 release [3787]http://stsdev.codeplex.com/workitem/3787If 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.<br />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?<br />bphillips76Thu, 16 May 2013 06:42:06 GMTClosed Issue: lastest code files miss essential pieces from 1.3 release [3787] 20130516064206AClosed Issue: Large WSP File Size [4102]http://stsdev.codeplex.com/workitem/4102If 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:<br /> <br />http://blogs.pointbridge.com/Blogs/monnette_jeff/Pages/Post.aspx?_ID=8<br />bphillips76Thu, 16 May 2013 06:42:05 GMTClosed Issue: Large WSP File Size [4102] 20130516064205AClosed Issue: Public Key Token Intermittently Not Generated Correctly for Feature Receiver on Project Creation [4751]http://stsdev.codeplex.com/workitem/4751I'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. <br /> <br />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.<br /> <br />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.<br />bphillips76Thu, 16 May 2013 06:42:05 GMTClosed Issue: Public Key Token Intermittently Not Generated Correctly for Feature Receiver on Project Creation [4751] 20130516064205ACommented Issue: System.IO.DirectoryNotFound on Win 2008 64-bit [2126]http://stsdev.codeplex.com/WorkItem/View.aspx?WorkItemId=2126Every time I tried to build my STSDev-based solution on my Windows 2008 64-bit machine, STSDev would crash out. I ran debug and it displayed the following error:<br /> Could not find a part of the path 'C:\Users\Administrator\Documents\Visual'.<br /><br />I recreated my solution at c:\sample and it compiles fine. So it looks like there may be a problem with spaces in the solution path in my configuration.<br />Comments: ** Comment from web user: jslicer ** <p>Same issue here, but no spaces in my path...</p>jslicerMon, 22 Feb 2010 21:38:12 GMTCommented Issue: System.IO.DirectoryNotFound on Win 2008 64-bit [2126] 20100222093812PCommented Issue: Empty <TemplateFiles /> node in manifest.xml [2571]http://stsdev.codeplex.com/WorkItem/View.aspx?WorkItemId=2571If there are no template files then an empty <TemplateFiles /> node is created in manifest.xml. This fails validation when calling addsolution.<br />Comments: ** Comment from web user: wlyq ** <p>still got the same error using 1.4</p>wlyqThu, 28 Jan 2010 20:30:05 GMTCommented Issue: Empty <TemplateFiles /> node in manifest.xml [2571] 20100128083005P