By Ben Dornis - 9/24/2007
We're having a problem here when StrataFrame is referenced these two files are also referenced. When we publish our website these files also get published, however, these two files are causing problems for the site and must be deleted each and every time. Is there anyway to ensure these files are not included?
-Ben
|
By Trent L. Taylor - 9/24/2007
What is the problem that is causes and your subject is cut off so I do not know exactly which DLLs you are referring to? Also, why can't you just exclude this in your install so they do not get pulled in?
|
By Ben Dornis - 9/25/2007
Microsoft.SqlServer.Reflection.dll
and
Microsoft.SqlServer.BatchParser.dll
As far as not including them in the install there is no way under asp.net that I am aware of in 2005 to exclude those files for publishing since they're not apart of the project and not referenced except, apparently, by Strataframe.
-Ben
|
By StrataFrame Team - 9/26/2007
The sad thing is that we don't reference them, but the Microsoft.SqlServer.Smo.dll that we reference does reference them, so, the dependency tree grabs them all. The only way that I can think of to not deploy the DLLs would be to either use the aspnet_compiler to compile the application to the location that you want (to the network share, not through FrontPage extensions), or to use a batch file in the after build event that will remove the DLLs from location after it is published.
|
By Ben Dornis - 9/27/2007
Good idea, I think I'll implement the batch option for now.
-Thanks
-Ben
|