Comments
Sort by recent activity
OK, if you go into Visual Studio (which ever edition you are building under) and under the "Tools" menu select "Options".
Under the "Projects and Solutions" section choose "Build and Run". You can then set the "MSBuild project build output verbosity" to one of the high settings.
There is a registry setting to do the same (e.g. if you can't run the IDE) HKCU\Software\Microsoft\VisualStudio\9.0\General
DWORD key "MSBuildLoggerVerbosity" with data "4" (diagnostic) or "3" (detailed), but usual warnings about editing your registry.
If you are building using the IDE version you will get all the detail straight-away. If you are using the command line version you should add the switch
/out <log file name>
to view the information (N.B. this is an append only log and with diagnostic will get quite big very quickly so turn off logging and reduce the verbosity as soon as you sort out the problem). / comments
OK, if you go into Visual Studio (which ever edition you are building under) and under the "Tools" menu select "Options".
Under the "Projects and Solutions" section choose "Build and Run". You can ...
Do you use a logger with MSBuild (e.g. http://msdn.microsoft.com/en-us/library/ms171470%28VS.80%29.aspx)?
The SmartAssembly.MSBuild.Task is configured to log errors and the errors from the actual build process will be sent to the log, although you may need to set the verbosity level to normal or detailed.
My guess if it works fine with the standalone command line, then it is a permissions or relative path issue. / comments
Do you use a logger with MSBuild (e.g. http://msdn.microsoft.com/en-us/library/ms171470%28VS.80%29.aspx)?
The SmartAssembly.MSBuild.Task is configured to log errors and the errors from the actual b...
Are you specifying an -output parameter as well? / comments
Are you specifying an -output parameter as well?
The full list of things which will give that error:
It can not find the main assembly as specified by the -input parameter or if -input is not given, the one in the project file. (The input parameter should either be an absolute path or a path relative to the project file name. Note it is not relative to the current working directory)
There is not a destination file name specified, either by the -output parameter or by the project file.
If you have asked to sign you assembly with a strong named key and the strong name key file does not exist.
If you are using the Automatic Error Reporting feature with a custom reporting template and it can not find the template specified or it is invalid.
If the project file specifies that one or more assemblies should be merged, but are not referenced by the main assembly.
My guess is either the second or the last are the problem.
Yes it would be better if SA actually told you what part of the configuration it was having problems with. / comments
The full list of things which will give that error:
It can not find the main assembly as specified by the -input parameter or if -input is not given, the one in the project file. (The input parame...
Nice idea.
You can add extra global search paths when you get prompted for missing references, although these are global for all SmartAssembly projects rather than just for the current project. / comments
Nice idea.
You can add extra global search paths when you get prompted for missing references, although these are global for all SmartAssembly projects rather than just for the current project.
Thanks for the feedback, I've raised an issues SA-297. / comments
Thanks for the feedback, I've raised an issues SA-297.
It is one of the fun things targeting the .NET Framework, the assembly resolution. In its project files SmartAssembly uses semi-full name resolution so an assembly called "myassembly" does not equal one called "myassembly, Culture=neutral, PublicKeyToken=xxxxxxx".
One big thing that should be noted is that SmartAssembly will always resolve the referenced assemblies from the main assembly itself. It only uses the listing in the project file to determine what settings to apply.
So having two entries in the project file about the "same" (one full, one partially named) assembly will not make any difference to the build process, however SmartAssembly will only apply the protection settings listed in the full named section.
The fact that the other entry is kept does have the nice benefit that if you have dynamic references (or even want to use the same project file for multiple assemblies via the command line... although we don't recommend this) you can add protection entries for all the assemblies you are likely to apply protection to and they will be protected when SmartAssembly finds them needed.
Generally we recommend using the GUI to edit the project file, although there are lots of times when we understand editing the file by hand is the easiest way. I suppose at some point we should give the file grammar, but I think the only gotcha is that the AssemblyName should be the .NET full name without version number. / comments
It is one of the fun things targeting the .NET Framework, the assembly resolution. In its project files SmartAssembly uses semi-full name resolution so an assembly called "myassembly" does not equa...
Sorry that is a known issue, partly related to the strong name signing issue discussed in http://www.red-gate.com/MessageBoard/viewtopic.php?t=11220.
The issue occurred in version 5.0 if you have any of the protection features that use compression ('resource compression and encryption', 'error reporting', or 'string compression and encryption') and tried to sign your assembly with a strong name key with a key size of more than 128 bytes.
It will be fixed in the forthcoming update.
I'll PM you with a temporary patch to fix the issue. / comments
Sorry that is a known issue, partly related to the strong name signing issue discussed in http://www.red-gate.com/MessageBoard/viewtopic.php?t=11220.
The issue occurred in version 5.0 if you have a...
Yes, that is why I suggested that workaround of reselecting the strong name key file as this refreshes the password.
Yes I know that it is a silly thing to have to do when upgrading projects, it is going to be formally documented in the update on Thursday. / comments
Yes, that is why I suggested that workaround of reselecting the strong name key file as this refreshes the password.
Yes I know that it is a silly thing to have to do when upgrading projects, it is...
I agree, I am in the middle of filing a bug report. / comments
I agree, I am in the middle of filing a bug report.