Build macros no longer working after upgrading from VS 2003 to VS 2005.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

WATYF1@gmail.com - 10 Jan 2007 14:35 GMT

I have a long and arduous deployment process set up, and although it
took me a while to get all the kinks out, it was all finally working
just great for many months.... and then I upgraded to VS 2005.

Part of this deployment process involves building my solution
(obviously) using a macro. The code I use to do that looks like this:

DTE.Solution.SolutionBuild.SolutionConfigurations.Item("Release").Activate()
DTE.Solution.SolutionBuild.Build(True)

...again... this worked just fine... for a long time.

But now that I'm on 2005, it doesn't seem to want to work. And that's
not to say that it gives me any errors... oh no... that would be way
too convinient. It just runs, but doesn't really do what it's supposed
to. After running the Release Build (which I double and triple and
quadruple checked is setup properly) it only builds SOME of the
projects in the solution. The remaining projects just don't get built
at all (and yes, those projects are included in the Release Build in
the configuration manager). It's the same projects every time that
don't build, and I can't find a way to get the build to actually build
my whole solution.

Now... if I manually build the solution by changing the build to
"Release" and hitting the "Build" button, then all those projects get
built just fine... it's only when I try to run the Build from code that
it doesn't work.

..anyone got any ideas on how to fix this?

WATYF

Reply to this Message

Mini-Tools Timm - 27 Jan 2007 23:14 GMT

Visual Studio 2005 macros do not work on Windows Vista for many people. This
is a huge problem for me because I use macros extensively in Visual Studio.

This is a known problem about which Microsoft has been conspicuously quiet.
Seems like very poor planning that Microsoft's flagship development
environment breaks on its flagship operating system. If you notice on the
forums, UAC has become the favorite excuse when anything goes wrong. Doesn't
work? Must be UAC!

On a related note, I just upgraded to Windows Vista. I started with a fresh
disk and clean install of Vista and all my software. I would highly
recommend AVOIDING upgrading to Vista for any production machines. In
general, about 1/3 of my software and hardware works fine on Vista. Another
third required some sort of upgrade or driver, typically requiring a fee.
And the final third had serious problems or didn't work at all. The latter
group includes Visual Studio macros, Elo Touch screens, WS_FTP Pro, some
Dreamweaver features, etc. When I spoke with one vendor (Elo), they said,
"Vista's not even released yet, is it?" I've spent two days upgrading to
Vista and am still dealing with issues like this Visual Studio macro problem.
I feel like "PC" in that commercial where I'm having to stay up all night
studying while my "Mac" buddy is off making home movies. :-P

To end on a nice note, Vista looks gorgeous and has many nice new features.

Signature

Timm Martin
Mini-Tools
.NET Components and Windows Software
http://www.mini-tools.com

Reply to this Message

Build macros no longer working after upgrading from VS 2003 to VS 2005.

Free Magazines