C# project after VS.NET 2005 SP1

[uupi_duu]

Hello,

Has VS.Net 2005 SP1 changed C# WebApp's project files?
Can't open it anymore without installing SP1.

Anyone know what is behind this?

Cheers,

 

[Mark Rae]

Has VS.Net 2005 SP1 changed C# WebApp's project files?
Can't open it anymore without installing SP1.

Yes and no... SP1 includes Web Application Projects, which was available
previously as an add-in - this was in response to the outcry from the web
development community when the project / solution model from v1.x was
dropped in v2 in favour of the website model, which most web developers
hated...

However, this should not have affected any existing web projects built in
the website model...

When you say you "can't open it any more", what actually happens when you
try...?

 

[uupi_duu]

Yes and no... SP1 includes Web Application Projects, which was available
previously as an add-in - this was in response to the outcry from the web
development community when the project / solution model from v1.x was
dropped in v2 in favour of the website model, which most web developers
hated...

However, this should not have affected any existing web projects built in
the website model...

When you say you "can't open it any more", what actually happens when you
try...?

Hello,

E.g. with Web Service projects Studio says it can't open projectfile
(or solution).

I also noticed that file called Microsoft.WebApplication.targets was
generated by Studio with SP1
and MSBuild.exe gives errors about it when MsBuild is used in computer
without SP1.

After installing SP1 everything works but without SP1 they will not.
And I can't install SP1 to Customer's computers.

Cheers,

 

[Mark Rae]

After installing SP1 everything works but without SP1 they will not.
And I can't install SP1 to Customer's computers.

When you say "customers' computers", are you actually developing e.g. code
libraries for your customers' developers...?

If so, then your customers' developers should be installing SP1 anyway, as
it includes not only Web Application Projects but also a huge number of bug
fixes and enhancements in areas of stability, perfomance and security...

 

[uupi_duu]

Come on, don't 'file smooth' the point,
of course many customers have developer's workstations
and source code is quite often compiled in their machines.

The actual point is that if Web project is opened in Visual Studio.Net
2005
with SP1 it does not open in Visual Studio.Net 2005 without SP1.
That is a problem with many 'customers'.

Do you think that a customer that use 10 - 15 vendors which may have
dozen of different SPs in future will allways upgrade or downgrade
their Studios?
Compatibility is the key point. I thing we should let 'customers' want
what they want ... or they don't pay anything

 

[Mark Rae]

Compatibility is the key point. I thing we should let 'customers' want
what they want ... or they don't pay anything

Good for you! In that case, then, it is you who are at fault, not your
customers because (by your own admission) you are not giving them what they
want...

If you need to provide that level of granular support, then you will need
two machines (or one machine and one virtual machine), one of which has
VS.NET 2005 and the other which has VS.NET 2005 + SP1...

 

[VJ]

SP1 takes backward compatibility out?.. Very scary...

VJ

 

[uupi_duu]

Good for you! In that case, then, it is you who are at fault, not your
customers because (by your own admission) you are not giving them what they
want...

If you need to provide that level of granular support, then you will need
two machines (or one machine and one virtual machine), one of which has
VS.NET 2005 and the other which has VS.NET 2005 + SP1...

Holy Cow, this forum is for developers not for Net Police or
Philosophies.