1

Resolved

STSDEV created VS project doesn't compile due to file references

description

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.

comments

bphillips76 wrote Aug 14, 2009 at 3:16 AM

Version 1.4 has now been released and includes this fix.

wrote Feb 14, 2013 at 1:35 AM

wrote May 16, 2013 at 6:42 AM

wrote May 16, 2013 at 6:42 AM

wrote Jun 14, 2013 at 8:02 AM