Macros as Post Build Events?

[ChrisB]

I have a number of things that I need to do on my assemblies after a release
build which I'm currently doing by executing a VBS file as a post build
event. Things include Dotfuscating, re-singing using sn.exe and copying all
the resulting files to a separate production folder.

Is there a better way of doing this? Using the VBS file seams like a rather
old fashioned (and un-managed!) way of this. How else can I go about
executing all these tools and copying all the resulting files whilst taking
advantage of Dot Net? How about using Visual Studio Macros?

Many thanks,
ChrisB.

[krishna.bitla]

Hi Chris,

Create a dotnet deployment package and add all these rules to the
package. When you create a deployment package, and compile the solution
it would give you the .exe and .msi files which you can use for
installing on any desired machine.

Cheers,
Kris

[ChrisB]

Hey Kris, thanks for the response.

Unfortunately we cant do that as the compiled assemblies once dotfuscated
and resigned have to go to a different department to then get packaged up
before going out the door. This would otherwise be the perfect way of doing
what needs to be done.

I'm probably not the only one who has their hands tied in this way, and I
hate the messy work arounds that I always end up having to do! I'm just
trying to find the best way I can do all this post build stuff in a managed
way, and drop the Notepad editing of the VBS files!

Any ideas?
<kr***********@gmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...

Hi Chris,

Create a dotnet deployment package and add all these rules to the
package. When you create a deployment package, and compile the solution
it would give you the .exe and .msi files which you can use for
installing on any desired machine.

Cheers,
Kris