Hi Alexander,

> I have to agree with Alex.  I've been doing exactly the thing he
recommends,
> and I never see locking issues.  I've got several dll's that are much
larger
> than 64k, some up to 3 times larger, and still no problems.

I completely understand this. However, as I've told Alex elsewhere ( :) ), I
do not agree with this. Doing all of this should be _completely_
unnecessary, we're just getting cramped with it because of bugs in the IDE,
that, at least to me, should have been fixed years ago. We saw this in the
original VS.NET beta cycle, so it's not like it's a new issue.

And while we're are it, the problem that causes the IDE's inability to build
to a common directory is just plain  crappy. Again, this should've been
fixed months ago.

Let me put it this way: If I can do everything we've talked about here with
the command line compiler without a single problem, why can't I do it using
the IDE? (and don't even get me started on the VC# project model, for christ
sake). We're supposed to be using IDEs to make it _easier_ to create and
build our projects, not harder.

Now, don't get me wrong. I think VS.NET is a superb tool in many aspects,
but, to me, it is utterly useless as a build tool for the projects I work
on. I've comed to distrust the VC# build engine so much, that I don't even
use it for fairly simple projects. Any project I'm even remotely serious
about, I use NAnt to build instead.

Of the whole lot of languages in the IDE, the only one that has a working
project model is VC++. That's just plain sad...

OTOH, I think this is getting seriously off-topic for this list, though :)
--
Tomas Restrepo
[EMAIL PROTECTED]

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to