Go Back   Velocity Reviews > Newsgroups > DotNet
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply

DotNet - Use command line option '/keyfile' or appropriate project settings instead of 'AssemblyKeyFile'

 
Thread Tools Search this Thread
Old 06-15-2006, 12:24 PM   #1
Default Use command line option '/keyfile' or appropriate project settings instead of 'AssemblyKeyFile'


Hi

I am in the Process of conversion of my existing 1.1 Dotnet Code to 2.0
framework.

for each project when i compile in VS2005 , i get this error\warning:

Use command line option '/keyfile' or appropriate project settings instead
of 'AssemblyKeyFile'

Question :

1. which is the best way to convert my assembly key file from its relative
path"..\\..\..\test.snk" to the way .Net Framework 2.0 needs??
2. i have this file in multiple projects (around 300 projects), any short
cut methods so that i can create a utility and update the location of my Snk
???

thanks
Senthil






SenthilVel
  Reply With Quote
Old 08-04-2006, 03:50 AM   #2
dd_fruend
Junior Member
 
Join Date: Aug 2006
Posts: 1
Question Got The Same Problem

It Is After Converting To Dotnet 2005
Did You Find A Solution ?
dd_fruend is offline   Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump