Re: strong name error
- From: "Nicole Calinoiu" <calinoiu REMOVETHIS AT gmail DOT com>
- Date: Mon, 10 Jul 2006 08:49:50 -0400
"Tom" <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:23E74076-49CE-4FAB-9077-CF46C1708832@xxxxxxxxxxxxxxxx
In VS 2005, it appears to me that I know longer have the ability to
conditionally sign the assemblies. If that is wrong, please jump in right
here...!!!!
Conditionally signing of assemblies is still possible, even when specifying
signing behaviour via the project properties. However, the UI does not
support the full flexibility required for this, so you'll need to do a bit
of manual editing of the build properties. Try this...
1. Remove all assembly-level attributes previously used to specify signing
behaviour.
2. Specify your preferred signing behaviour for release builds using the
project properties editor then save your project.
3. In the solution explorer within VStudio, right-click the node for your
project, then select "Unload Project" from the context menu.
4. Once the project is unloaded, right-click the project node again, and
select the "Edit <your project>.csproj" item from the context menu.
5. Manually edit the csproj file to move the SignAssembly and
AssemblyOriginatorKeyFile nodes from the default property group to the
release property group.
6. Save the file then reload the project from the project context menu.
Other than having to be careful not to place signed DEBUG code into the
production area, is there something else I should be on the watch for???
So
how am I doing thus far....??? Am I about to screw myself up and not yet
see
it coming?!?!?
Personally, I would be quite concerned about deploying signed assemblies
when most (or all?) testing was performed on their unsigned counterparts.
Is there some particular reason you are avoiding use of delay signing for
your debug assemblies? If you are concerned about the risks exposed by
verification skip entries, you might want to consider using the new test key
signing functionality available in fx 2.0. (See
http://msdn.microsoft.com/msdnmag/issues/06/07/CLRInsideOut/default.aspx for
an overview and http://blogs.msdn.com/shawnfa/archive/2005/10/24/484170.aspx
for more details.)
.
- Prev by Date: Re: Security Exception with DataSet.ReadXML
- Next by Date: Re: Overriding non-virtual methods using IL and Reflection.Emit
- Previous by thread: Security Exception with DataSet.ReadXML
- Next by thread: Converting HTML page to PDF in .NET
- Index(es):
Relevant Pages
|
