.NET 2003 no longer shows which file are exluded from current build

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

rob - 25 Sep 2003 12:18 GMT

<moan>
In vc6 and .NET 2002, files in the project/solution window would indicate
that they were built (or not) under the current configuation by a little
down arrow (or not), so if you were working on cross-platform code you could
easily see what was excluded from the current build.

In .NET 2003, this useful feature has been removed, and now you get a tiny
'c++' on (guess what ?) c++ files, and 'h' on header files

aaarrgh!

</moan>

Is there anywhere I can raise this with any chance of it being 'fixed' ? Or
is there an option somewhere to turn it back on (ha) ?

Rob Anderson

Reply to this Message

Roger Austin - 29 Sep 2003 08:31 GMT

This is (one of the numerous) reasons why I will NOT be
upgrading from VSN to VSN2003. Another example of dumbing
down the IDE to suit .NET programmers at the expense of
C++ programmers. This "1 size fits all IDE" just isn't
working, but the Microsoft .NET train is unstoppable!

As for getting it fixed, I think not. There is so much
wrong with VSN2003 that you might have expected a service
pack to have been released by now. Looks like VSN2004 will
be the service pack for VSN2003, you will thus be "forced"
to upgrade to get your fixes in the future! Microsoft are
silent on this issue, but I have seen comments in other
posts from MS that problem X will be fixed in the next
release of VS.NET. I wish MS would come clean on this
issue.

>-----Original Message-----
><moan>
[quoted text clipped - 16 lines]
>
>.

Reply to this Message

.NET 2003 no longer shows which file are exluded from current build

Free Magazines