How can I tell the difference between source and published .NET code?
-
How can I tell the difference between source and published .NET code? I am looking at some inherited code that I have not touched in about a year. The original designer had me first publish locally before uploading the published code to the internet server. Now I am looking a number of backed up source folders as well bas backed up published folders. I should have done a better job at naming the folders, I guess. Now I wonder: How can I tell the difference between source and published .NET code? Is there some easy way to see if some folder that contains only published code is lacking a file or xml setting? Is the .csproj file or the .sln file part of the code pushed to the server when you publish?
-
How can I tell the difference between source and published .NET code? I am looking at some inherited code that I have not touched in about a year. The original designer had me first publish locally before uploading the published code to the internet server. Now I am looking a number of backed up source folders as well bas backed up published folders. I should have done a better job at naming the folders, I guess. Now I wonder: How can I tell the difference between source and published .NET code? Is there some easy way to see if some folder that contains only published code is lacking a file or xml setting? Is the .csproj file or the .sln file part of the code pushed to the server when you publish?
-
Published code contains only the files needed for the app to run and it does not contain .csproj or .sln files.
Hm... Normally, the web server won't throw an exception if csproj and sln files are deployed also...
-
Hm... Normally, the web server won't throw an exception if csproj and sln files are deployed also...
Well, no - but it's not automatic. (And I'd rather not do it, it's untidy and prone to error) I'd probably include a version number and a build timestamp, as I do in my non-website code.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
Hm... Normally, the web server won't throw an exception if csproj and sln files are deployed also...
-
How can I tell the difference between source and published .NET code? I am looking at some inherited code that I have not touched in about a year. The original designer had me first publish locally before uploading the published code to the internet server. Now I am looking a number of backed up source folders as well bas backed up published folders. I should have done a better job at naming the folders, I guess. Now I wonder: How can I tell the difference between source and published .NET code? Is there some easy way to see if some folder that contains only published code is lacking a file or xml setting? Is the .csproj file or the .sln file part of the code pushed to the server when you publish?
Xarzu wrote:
Is the .csproj file or the .sln file part of the code pushed to the server when you publish?
When I deliver something to production it is - In source control - Labeled in source control - Built from source control - Delivered from that build Other than that I either keep track of the label that went to production and when. Or I specifically re-label using a build version number with a label that indicates a production delivery.
