Re: Re: VS.NET 2002 solution

David Waite <[email protected]> Mon, 15 Sep 2003 18:09:42 -0600
Newsgroups gmane.comp.sourceid.sso.devel
Message-ID <[email protected]>
Daniel, Matthew wrote:

>I am terribly sorry to follow-up my own post, but ... [which is the
>start of all good posts]
>
>My trusty copy of Vim and I had a conversation with these .sln and
>.csproj files, resulting in the ability to open and build the projects
>in VS.NET 2002. There are still some issues surrounding the
>delay-signing, as it works great from NAnt but not from VS.NET
>(sp-sample throws unsigned exceptions).
>  
>
Glad to hear you coaxed the solution files into opening under VS.NET 
2002. As a side note, the visual debugger should be able to map the 
compiled files to the source code location; you can use the .NET 
framework included CLR debugger or attach the VS.NET debugger if you 
have built a local copy.

VS.NET does not do delay signing itself, and the distributed 
SourceID.NET package does not include the public key (so that official 
packages can be trusted.) In the included readme there is a line which 
turns on key exemption for that particular public key:

sn.exe -Vr *,8c869275329aeb85

This is not recommended for deployment, however. Either deploy with the 
official versions, or substitute a locally-generated keypair.

-David Waite