By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,606 Members | 2,016 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,606 IT Pros & Developers. It's quick & easy.

Signing a vb.net class using a post build event macro

P: n/a
We use buildit to automatically build all of our solutions every
night. In C# we are able to call a batch file for the post build
event and sign the assembly for the GAC using our private/public key
pair.

Now, in VB.net there's no easy way to do this. I saw that you can
create a macro that catches the bldevents.OnBuildDone event, but this
is only for when the solution finishes. We have an InstallShield X
project as part of the assembly, so signing the assembly after the
solution finishes building is too late. Also, I don't see any real
documentation on this EnvDTE class, how can I get the path to a
certain project's output?

Does any have any experience or suggestions with how to proceed? I
think we will just separate the installer project from the solution,
but it'd be nice to just have one solution either build or not...

Thanks,
Graham
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I'd just create a "dummy" c# project in the solution with a dependency on
the VB project that has a post-build event. It's a little bit of a hassle,
but hopefully that'll be fixed in the next version.
-Mike

"Graham" <si****@gmail.com> wrote in message
news:d8**************************@posting.google.c om...
We use buildit to automatically build all of our solutions every
night. In C# we are able to call a batch file for the post build
event and sign the assembly for the GAC using our private/public key
pair.

Now, in VB.net there's no easy way to do this. I saw that you can
create a macro that catches the bldevents.OnBuildDone event, but this
is only for when the solution finishes. We have an InstallShield X
project as part of the assembly, so signing the assembly after the
solution finishes building is too late. Also, I don't see any real
documentation on this EnvDTE class, how can I get the path to a
certain project's output?

Does any have any experience or suggestions with how to proceed? I
think we will just separate the installer project from the solution,
but it'd be nice to just have one solution either build or not...

Thanks,
Graham

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.