Please vote on this suggestion...

[Urs Eichmann]

Make (at least Class Library) Projects shareable between VS 2003 und 2005

http://lab.msdn.microsoft.com/produc...1-72fd99a18693

Thank you!
Urs

[Stephany Young]

I will not be voting for it.

In my opinion, adding a file to both projects and keeping them is sync is a
matter of someone doing their job properly, in other words, a managerial
function. I do not expect MS to add functionality to save me from myself.

If you've got people who can't manage a simple exercise like keeping 2
projects in sync then what are you going to do when someone adds some
FrameWork 2.0 specific code into a 'library' and then someone else attempts
to compile the Framework 1.1 the project?
"Urs Eichmann" <ur***@online.n ospam> wrote in message
news:OF******** ******@TK2MSFTN GP09.phx.gbl...

Make (at least Class Library) Projects shareable between VS 2003 und 2005

http://lab.msdn.microsoft.com/produc...1-72fd99a18693

Thank you!
Urs

[Daniel]

Me neither. I totally agree, this would be a bad idea.

--

Daniel
MCSE, MCP+I, MCP in Windows 2000/NT

--------------------------------------
remove the 2nd madrid from my mail address to contact me.

"Stephany Young" <noone@localhos t> wrote in message
news:Ov******** ******@TK2MSFTN GP14.phx.gbl...

I will not be voting for it.

In my opinion, adding a file to both projects and keeping them is sync is
a matter of someone doing their job properly, in other words, a managerial
function. I do not expect MS to add functionality to save me from myself.

If you've got people who can't manage a simple exercise like keeping 2
projects in sync then what are you going to do when someone adds some
FrameWork 2.0 specific code into a 'library' and then someone else
attempts to compile the Framework 1.1 the project?
"Urs Eichmann" <ur***@online.n ospam> wrote in message
news:OF******** ******@TK2MSFTN GP09.phx.gbl...

Make (at least Class Library) Projects shareable between VS 2003 und 2005

http://lab.msdn.microsoft.com/produc...1-72fd99a18693

Thank you!
Urs

[Herfried K. Wagner [MVP]]

"Stephany Young" <noone@localhos t> schrieb:

I will not be voting for it.

In my opinion, adding a file to both projects and keeping them is sync is
a matter of someone doing their job properly, in other words, a managerial
function. I do not expect MS to add functionality to save me from myself.

Mhm... Maybe support for adding a project reference in VS 2005 to the
VS.NET 2003 class library that will open in a separate instance of VS.NET
2003 is the be better approach, especially for very large projects
consisting of lots of projects. I agree with Urs that migration from VS.NET
2003 to VS 2005 will be harder without some sort of integration of VS.NET
2003 projects into VS 2005.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Herfried K. Wagner [MVP]]

"Daniel" <gr****@madridm adridsoleado.co m> schrieb:

Me neither. I totally agree, this would be a bad idea.

I don't like the idea too, but this doesn't mean that the problem doesn't
exist.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Stephany Young]

I wasn't saying that I don't recognise potential problems.

What I didn't agree with was, specifically, the proposal, for the reasons I
gave.
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:uz******** ******@TK2MSFTN GP09.phx.gbl...

"Stephany Young" <noone@localhos t> schrieb:

I will not be voting for it.

In my opinion, adding a file to both projects and keeping them is sync is
a matter of someone doing their job properly, in other words, a
managerial function. I do not expect MS to add functionality to save me
from myself.

Mhm... Maybe support for adding a project reference in VS 2005 to the
VS.NET 2003 class library that will open in a separate instance of VS.NET
2003 is the be better approach, especially for very large projects
consisting of lots of projects. I agree with Urs that migration from
VS.NET 2003 to VS 2005 will be harder without some sort of integration of
VS.NET 2003 projects into VS 2005.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Urs Eichmann]

>>>In my opinion, adding a file to both projects and keeping them is sync is

a matter of someone doing their job properly, in other words, a
managerial function. I do not expect MS to add functionality to save me
from myself.

Of course it is a matter of doing the job properly. But believe me,
sooner or later you *will* forget to add the new file to the other
solution, because you're under pressure or have a bad day or whatever...

With the same reason you could argue that there should be no Garbage
Collector in .NET, because if everyone gets rid of the memory used by
their objects properly, there would be no need for it... but as can be
seen in reality, this is not always the case and a GC is desperately
needed. C++ people try to do it without GC... that's where all the
Memory leaks come from...

Im my opinion syncing between two Projects is a fully automatable
process - and what CAN be automated SHOULD be, otherwise there will be a
mistake creeping in sooner or later.

[Stephany Young]

Comparing it to the GC is just a nonsense.

The operation of the GC has absolutely nothing to do with adding a source
file to one or more projects in the IDE.

If YOU really want it then write an add-in to do it for you. Don't expect MS
to force something that you happen to want upon everybody else, especially
those who specifically don't want it.

There are lots of things that I would like to have in either the .NET
runtime or the VS.NET IDE. If I really want them then I write them myself.
Then they do exactly what I want.
"Urs Eichmann" <ur***@online.n ospam> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

In my opinion, adding a file to both projects and keeping them is sync
is a matter of someone doing their job properly, in other words, a
manageria l function. I do not expect MS to add functionality to save me
from myself.

Of course it is a matter of doing the job properly. But believe me, sooner
or later you *will* forget to add the new file to the other solution,
because you're under pressure or have a bad day or whatever...

With the same reason you could argue that there should be no Garbage
Collector in .NET, because if everyone gets rid of the memory used by
their objects properly, there would be no need for it... but as can be
seen in reality, this is not always the case and a GC is desperately
needed. C++ people try to do it without GC... that's where all the Memory
leaks come from...

Im my opinion syncing between two Projects is a fully automatable
process - and what CAN be automated SHOULD be, otherwise there will be a
mistake creeping in sooner or later.

[Urs Eichmann]

Stephany Young wrote:

Comparing it to the GC is just a nonsense.

The operation of the GC has absolutely nothing to do with adding a source
file to one or more projects in the IDE.

I disagree. In both situations, it is an automatism which wants to
relieve the developer from error-prone work which he *clould* to
manually, but it is better if it is automated because the end product
will be less faulty.

But if you want, another situation: Why is there SCC integration in
Visual Studio? After all, you could check-in and check-out your files by
hand outside the IDE. But it would lead to much more errors (forgetting
to check-in files and so on), because people tend to forget things if
they have to do a task in multiple places.

Urs

[Stephany Young]

Whatever ...
"Urs Eichmann" <ur***@online.n ospam> wrote in message
news:eA******** ******@TK2MSFTN GP15.phx.gbl...

Stephany Young wrote:

Comparing it to the GC is just a nonsense.

The operation of the GC has absolutely nothing to do with adding a source
file to one or more projects in the IDE.

I disagree. In both situations, it is an automatism which wants to relieve
the developer from error-prone work which he *clould* to manually, but it
is better if it is automated because the end product will be less faulty.

But if you want, another situation: Why is there SCC integration in Visual
Studio? After all, you could check-in and check-out your files by hand
outside the IDE. But it would lead to much more errors (forgetting to
check-in files and so on), because people tend to forget things if they
have to do a task in multiple places.

Urs