|
|
nice to have such reason
for us was reason 'it must be better'
|
|
|
|
|
|
As soon as VS2005 represents the stable development tool I wanted from VS2003, I'll use it and I'll "migrate" my team onto it.
BUT, if VS2005 is not leaps ahead of VS2003 in terms of stability and reduced limitations, then I'll give this one a skip.
I had a Windows form designer corrupt in VS2005 beta 1 and I had to shut down the IDE.
I can't tell you how often we get this in VS2003. 
Cheers,
Simon
sig ::
"Don't try to be like Jackie. There is only one Jackie.... Study computers instead.", Jackie Chan on career choices.
article :: animation mechanics in SVG blog:: brokenkeyboards
"It'll be a cold day in Hell when I do VB.NET...", Chris Maunder
|
|
|
|
|
Nishant S wrote:
I wonder how many people are using VS.NET Whidbey for production code
I voted for it because I am doing testing with it. No production code development is being done with it - although looking at some of the new features available (with the IDE and the language and .NET Framework enhancements) I can't help being impatient.
Do you want to know more?
Not getting the response you want from a question asked in an online forum: How to Ask Questions the Smart Way!
|
|
|
|
|
First of all I've to say that we use (at present) only the C++ compiler with unmanaged code.. ( so no C#, ASP, etc. with reselled product)
I'll use 2003 version for production code but I'll test (weekly) all code with Whidbey to insure future portability (and I'm still working on porting all legacy code to work in both environment... really form some cases also with VC 6.00).
Tha same approach with SQL Server 2000 and Yukon.. We try to prepare ourself to the day we need to change version
Davide
|
|
|
|
|
I would guess 0.
Do you think or have you heard of anybody, in your experience, who use production tools especially those like VS.NET for production?
Just curious... 
« Superman »
|
|
|
|
|
>who use production tools especially those like VS.NET for production
VS.NET? As in 2002 or 2003? Plenty of people use those for production code, especially in web-dev circles thanks to ASP.NET.
2005, hopefully nobody or very few do.
regards,
Paul Watson
Bluegrass
South Africa
Michael Dunn wrote:
"except the sod who voted this a 1, NO SOUP FOR YOU"
Crikey! ain't life grand?
|
|
|
|
|
Sorry, I meant the beta version. I use 2003 myself, mostly for non-web development.
« Superman »
|
|
|
|
|
I use it for editing production XSL templates, as the editor in VS2k5 provides better support for this than VS2k3 does. That's about it though.
You're one microscopic cog
in his catastrophic plan...
|
|
|
|
|
I mainly use VS 2003 for live code, but already use VS 2005 for production that will be released after VS2005 goes live (RTM).
I find VS 2005 pretty stable although some things are a little harder to do (unfinished features).
So basically I use it for production code
Speak Out! Use the Source, Luke!
(Dr. GUI .NET #5)
|
|
|
|
|
Hopefully none. It's against the usage policy and terms to use it for production. On top of that... it's still in beta and greatly unstable. I'm using it just to play around with and get geared up for the release of it. I hope they hurry (ha).
Edited: I accidentally said that it was "stable". Oopsie.
Manuet Systems
http://www.manuet.com
|
|
|
|
|
I am currently not using VS2005 for production code. This is simply because the program is not ready.
But I use VS2005 for testing purposes of future applications. Like my own application core, which I hope to finish next year 
"Every rule in a world of bits and bytes can be bend or eventually be broken"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
