tags:

views:

402

answers:

2
Q: 

How to give a .net 1.1 dll a strong name in VS2003

I have a .net 1.1 dll I need to digitally sign for a legacy project. I have created a .snk file. What steps must I take in Visual Studio to apply the signature?

Edit: Found this http://www.robrich.org/archive/2006/11/29.aspx

+1  A: 

Maybe these links will be helpfull:

Strong name WinForms 1.1

.NET Framework 1.1 Security Guidelines - Strong Names

Paul G.  2009-02-09 18:22:04
A: 

prepare a key file to give strong name **ex: sn.exe -k test.dll test.snk

 2009-04-28 07:57:02

related questions

Integrating Diff Tools With Visual Studio 2003
Visual Studio 2003 - opening ASP.NET project - getting "The operation timed out" error message
[Visual Studio 2003] Setting environment variables in pre-build event and using in compilation step
What should I look out for when migrating a project from VS2003 to VS2005
VS.NET 2003 and VS.NET 2008 co-existence
Opening a VS 2003 C++ project in VS 2008
What code changes are required to migrate C++ from VS2003 to VS2005?
Anyone Know a good tutorial of how Crystal Reports for Visual Studio works?
Compile 32 bit VS 2003 project to 64 bit
Problem to porting managed c++ from vs2003 to vs2008
Developing for Sharepoint 2003 using Visual Studio 2008?
Moving from vb.NET (2003) to vb2005 What are some of the benefits?
Visual Studio 2003 Merge Modules
Error Message: "Access to the path c:\windows\microsoft.net\framework\(version)\Temporary ASP.NET Files\(blah) is denied." - what causes this?
How to build a solution to target 64 bit environment?
Omitting XML processing instruction when serializing an object
How to detect design time in a VS.NET 2003 control library project
How to setup non-admin development in Visual Studio 2005 and 2003
VS2003/05 constantly screws up the display - is there any known fix for this?
VS 2003 CrystalReports - details section problem
VS 2003 Reports "unable to get the project file from the web server" when opening a solution from VSS
Is Visual Studio 2003 still available/supported
Attaching to a foreign executable in Visual C++ 2003
I can't get my debugger to stop breaking on first-chance exceptions