This is a great example of code style guide used by Microsoft for internal coding. I’ve included a sample of it below. Enjoy!!!
Tag: .net
.Net 1.1, Visual Studio 2003, and TFS 2010
So, you have some old .Net 1.1 apps that you don’t want to upgrade, BUT you want to use TFS 2010 for your source control. Well you are in for a treat! (kidding)
First, you’re condemned to using VS 2003, because VS 2005, 2008, and 2010 only deal with .Net 2.0 and higher.
Second, because of this, you’re condemned to using the TFS 2010 MSSCCI provider; which is a not very well documented, unsupported by MS free tool. 🙂 (Have fun)
This guy has a great post with screenshots to lead you through the gauntlet!
Third, heaven help you if you’re migrating your source from another source control provider like SourceSafe or PVCS. You’ll need to unbind the code from the old source ccontrol provider and then re-bind it to TFS 2010. A treachous course that shouldn’t be taken lightly.
But otherwise, have fun!
Check to see if an assembly is strongly named.
Type sn -v NameOfAssembly.dll at the command line. It will say “NameOfAssembly.dll is valid” if it is strongly named. It will say “NameOfAssemby.dll does not represent a strongly named assembly” if it is not.
Example:
c:\>sn -v Microsoft.AnalysisServices.AdomdClient.dll
Microsoft (R) .NET Framework Strong Name Utility Version 4.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
Assembly ‘Microsoft.AnalysisServices.AdomdClient.dll’ is valid
