Studio 2005! Is that a satisfactory product?
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
Sameers (theAngrycodeR ) wrote:
Hope these things will vanish in next release of studio!
:laugh::laugh: That's funny! I don't expect any drastic improvements. Even if they vanish be prepared to see new issues.
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
stupid errors "file is locked and can not write {\build_path\ProjectName.dll} what's so stupid about this error? Long delay to update property window in web designer view I've heard this is blistering fast on a Dual Cray system. There are quirks and issues, and in many places it's definitely to sluggish. My main problem is the sheer amount they put into the addin interface, and then turned it into a PITA by some open ends. The C# stuff at least outweights all the crap, though.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighist -
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
Have you tried running on a machine that doesn't have a virus scanner? - I found the bulk of my VS and SQL Server problems went away when I uninstalled NAV.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
I can add to that list: - Rebuild doesn't work and you get the error .dll could not be found. (The assembly is the result of one of the projects in your solution) - When you build a project with custom workflow activities the designer fails reloading saying there's a problem with the assembly. (D'oh I have a new version) Restart VS2005 seems to fix that. But, this doesn't stop me from using VS2005, the code editor is great with the codesnippets and the refactoring features. It's just the designers that mess stuff up. I'm running Orcas Beta 1 on a VPC image, but it isn't much better then VS2005. It looks the same and the bugs are almost the same too. There's still a long way to go there.
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
Cant handle multpile (more than 30) connected projects in vb. I have to use msbuild. Wizards for db access are slow...:zzz:
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
Answer: we don't. Most of our development is carried out using Visual Studio 2003. For what it's worth, Visual Studio 2007 ("Orcas") looms like its shaping up to be far more stable than 2005. Compare VS2005 Beta 1 with VS2007 Beta 1 and you'll see what I mean...
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Although with the release of Servie Pack 1, it seems to be a bit better, but still, there looks lot of problems in it. Do you people face them? For example, build fails due to stupid errors "file is locked and can not write <\build_path\ProjectName.dll>, crash of Cassini web server when you detach your debugger (stop debugging). Long delay to update property window in web designer view, failure to update control names if you change in design view (not always though) and such other issues. Eventually, there are a lot of new features in 2005, but at the same time, lot of bugs/problems in it. How much of you face these problems? I see most of the times, Microsoft replies with bugs saying 'Unable to reproduce'. Hope these things will vanish in next release of studio! Sameers
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
I rarely have any problems with VS, apart from Intellisense giving out every few weeks (I code a lot :) Everything builds for me, runs for me, debugs for me, etc. just fine. I don't even have SP1, which I should get.
-
I rarely have any problems with VS, apart from Intellisense giving out every few weeks (I code a lot :) Everything builds for me, runs for me, debugs for me, etc. just fine. I don't even have SP1, which I should get.
Looks like you are the most lucky person in the world!
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
-
stupid errors "file is locked and can not write {\build_path\ProjectName.dll} what's so stupid about this error? Long delay to update property window in web designer view I've heard this is blistering fast on a Dual Cray system. There are quirks and issues, and in many places it's definitely to sluggish. My main problem is the sheer amount they put into the addin interface, and then turned it into a PITA by some open ends. The C# stuff at least outweights all the crap, though.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighistpeterchen wrote:
stupid errors "file is locked and can not write {\build_path\ProjectName.dll} what's so stupid about this error?
Looks like you never got such problem! Just think for a while, you build your project and you get this error and build fails. You try again and same thing happens. Maybe, on 10th try, you get success (or before each build, you have to restart studio).
peterchen wrote:
Long delay to update property window in web designer view I've heard this is blistering fast on a Dual Cray system.
Well, I think the speed of system doesn't matter for it. And If I am not worng, Microsoft committed this as a problem in studio.
peterchen wrote:
The C# stuff at least outweights all the crap, though.
I wish, I was C# developer then.
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
-
Have you tried running on a machine that doesn't have a virus scanner? - I found the bulk of my VS and SQL Server problems went away when I uninstalled NAV.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Really Not! But who can imagine life of computer without an anti-virus?
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
-
peterchen wrote:
stupid errors "file is locked and can not write {\build_path\ProjectName.dll} what's so stupid about this error?
Looks like you never got such problem! Just think for a while, you build your project and you get this error and build fails. You try again and same thing happens. Maybe, on 10th try, you get success (or before each build, you have to restart studio).
peterchen wrote:
Long delay to update property window in web designer view I've heard this is blistering fast on a Dual Cray system.
Well, I think the speed of system doesn't matter for it. And If I am not worng, Microsoft committed this as a problem in studio.
peterchen wrote:
The C# stuff at least outweights all the crap, though.
I wish, I was C# developer then.
FREE MSN Auto Responder[^] History Remember Vendors, NOT Developers
No, never had it. All I did under Vs2005 is C#, so that may be a reason. And as I read from the others, ASP.NET editor seems to really lag.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighist