R
Rod at Work
Guest
We're working on cleaning up some code in a WPF app that we've written. When I build the app on my PC I get this warning message:
"Assembly 'Binaries\Microsoft.SqlServer.Types.dll' is incorrectly specified as a file."
I've looked the warning message up and found several places online that basically said to set the Build Action to None. (e.g.: How to remove or correct the warning: "Incorrectly Assembly is specified as a file".) However I'm concerned about deploying the Microsoft.SqlServer.Types.dll. This app does happen to be a ClickOnce deployment type of app. That DLL does happen to have its Build Action property set to Content. The Copy to Output Directory property is set to Copy if never. If I set the Build Action to None and leave Copy to Output Directory set to Copy if newer, is that sufficient to guarantee that Microsoft.SqlServer.Types.dll will be deployed to our target machines?
Rod
Continue reading...
"Assembly 'Binaries\Microsoft.SqlServer.Types.dll' is incorrectly specified as a file."
I've looked the warning message up and found several places online that basically said to set the Build Action to None. (e.g.: How to remove or correct the warning: "Incorrectly Assembly is specified as a file".) However I'm concerned about deploying the Microsoft.SqlServer.Types.dll. This app does happen to be a ClickOnce deployment type of app. That DLL does happen to have its Build Action property set to Content. The Copy to Output Directory property is set to Copy if never. If I set the Build Action to None and leave Copy to Output Directory set to Copy if newer, is that sufficient to guarantee that Microsoft.SqlServer.Types.dll will be deployed to our target machines?
Rod
Continue reading...