Visual studio 2008, is it worth it?
-
The JavaScript debugging is improved, so if you do a lot of IE JS debugging, that might be worth it.
----
You're right. These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets.
If you're using telerik controls turning on javascript debugging will ruin your life, IMO. All their controls seem to throw loads of javascript errors that get in the way of debugging any hand coded javascript. Also adding other Ajax Controls from other toolkits to the page also seems to break Telerik controls. I know this isn't a Telerik thread but I just have to say, I hate strongly dislike Telerik controls.
-
I hopped from vs2003, to vs2005 and finally to vs2008. There are some good improvements to the framework like System.Timezone and Visual Studio 2008 SP1 performs much better than any of its predecessors, especially where web development is concerned. Think about it... if your about to embark on a major cycle now, best to bring your tools up to date before you start, especially with all those 3rd party library dependencies. I know from my own experiences that the telerik controls perform a lot better in recent versions. I am certainly glad i did it ;P
---Guy H ;-)---
Guy Harwood wrote:
There are some good improvements to the framework like System.Timezone and Visual Studio 2008 SP1 performs much better than any of its predecessors, especially where web development is concerned.
2005 was slower for webwork? 2008's
InfuryatingMultisecondUiDelay(5)calls when editing aspx pages is maddening enough. By the end of the short project I was almost to the point of using textpad for my aspx editor and giving up the syntax highlighting and autocomplete that VS offered.Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
Guy Harwood wrote:
There are some good improvements to the framework like System.Timezone and Visual Studio 2008 SP1 performs much better than any of its predecessors, especially where web development is concerned.
2005 was slower for webwork? 2008's
InfuryatingMultisecondUiDelay(5)calls when editing aspx pages is maddening enough. By the end of the short project I was almost to the point of using textpad for my aspx editor and giving up the syntax highlighting and autocomplete that VS offered.Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
dan neely wrote:
2005 was slower for webwork? 2008's InfuryatingMultisecondUiDelay(5) calls when editing aspx pages is maddening enough. By the end of the short project I was almost to the point of using textpad for my aspx editor and giving up the syntax highlighting and autocomplete that VS offered.
:rolleyes:
---Guy H ;-)---
-
Yes, it's definately worth the upgrade. I would actaully say go straight to VS2008 SP1 as well. There have been a lot of IDE improvements (usability features and speed) and improvements in the web development experience as well including better JS and CSS support.
Scott Dorman
Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
I would caution against using the SP1 for VS 2008 if you are trying to debug large multi-threaded/multi-appdomain applications. It will stop at your first break point and then ignore the rest. Most frustrating, we had to drop VS 2008+SP1 and reinstall VS 2008 to clean it up.
-
ToddHileHoffer wrote:
It is too bad you can't do 3.5 development
I can, I investigated it thoroughly and could see no benefit at all to it and in fact many down sides and have chosen not to use it. I have a lot of hand crafted code for getting my objects into and out of the database and performance wise it's much faster. As well we aren't married to MS SQL server as we have a db independant layer between the database and the business object framework so we can support FireBird and MS SQL and whatever else comes along that starts getting wide usage. I'm not big on stored procedures, in fact I'm very much against them but that's a discussion for another thread. :)
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
John C wrote:
I'm not big on stored procedures, in fact I'm very much against them but that's a discussion for another thread.
I'd like to see that thread. We use stored procs for an added security layer (dynamic SQL leaves itself wide open for injection attacks much of the time) and also for processing that can't be simply left to a query, or where optimizations can be performed in lieu of what would otherwise be a standard query. However, if you've built your own db-independence layer, you're stuck with it until you have to throw it away. Back in '96, we certainly were.
-
John C wrote:
I'm not big on stored procedures, in fact I'm very much against them but that's a discussion for another thread.
I'd like to see that thread. We use stored procs for an added security layer (dynamic SQL leaves itself wide open for injection attacks much of the time) and also for processing that can't be simply left to a query, or where optimizations can be performed in lieu of what would otherwise be a standard query. However, if you've built your own db-independence layer, you're stuck with it until you have to throw it away. Back in '96, we certainly were.
cpkilekofp wrote:
We use stored procs for an added security layer (dynamic SQL leaves itself wide open for injection attacks much of the time)
True, but those types of problems can be mitigated without using stored procedures. Parameterized queries act a lot like stored procedures, without the need to store them on the database.
-
cpkilekofp wrote:
We use stored procs for an added security layer (dynamic SQL leaves itself wide open for injection attacks much of the time)
True, but those types of problems can be mitigated without using stored procedures. Parameterized queries act a lot like stored procedures, without the need to store them on the database.
Brad Stiles wrote:
True, but those types of problems can be mitigated without using stored procedures. Parameterized queries act a lot like stored procedures, without the need to store them on the database.
Yeah, and stored procedures don't need to be recompiled for every application instance, as parameterized queries do. Also, they can act as an abstraction layer for changes in the schema, guaranteeing you that you'll get the same recordset or output values back no matter how the schema changes. Further, that abstraction allows a database administrator whose focused attention can improve the performance and robustness of the stored procedure in complete independence of application distributions. If you're doing it all yourself, and you have limited knowledge of your data manipulation language (DML), then parameterized queries make the most sense. If you're guaranteed your schema will change or your perfomance needs will change no more frequently than your application code base, parameterized queries also make sense. I've worked on projects both ways, and the higher your need for performance and robustness, the more likely you are to move the data access code to the data server. No matter what you do to a parameterized query, it won't perform as well as a stored procedure except for the simplest operations. It can be a pain to maintain unless you use tools such as Visual Studio to edit (and debug, if your administrator permits) stored procedures and user-defined functions along with regular application code.
-
Argh, we moved from Resharper 3.1 to 4 & it's been a complete PITA ever since. I switch it off half the time now coz it's become a resource hog.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
John C wrote:
I'm not big on stored procedures, in fact I'm very much against them but that's a discussion for another thread.
My ideal world is that database access, XML and JavaScript are all completely abstracted away so that all you ever see is business logic and UI in high level code. :)
Kevin
Kevin McFarlane wrote:
My ideal world is that database access, XML and JavaScript are all completely abstracted away so that all you ever see is business logic and UI in high level code.
I would rather like to have the UI implementation "abstracted away" :-D
-
Ive noticed that too Resharper 4.1 is a real hog The 4.5 release is about speed and smaller footprint though
4.5 available yet? If it's beta is it stable?
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen -
Kevin McFarlane wrote:
My ideal world is that database access, XML and JavaScript are all completely abstracted away so that all you ever see is business logic and UI in high level code.
I would rather like to have the UI implementation "abstracted away" :-D
That as well. :)
Kevin
-
Argh, we moved from Resharper 3.1 to 4 & it's been a complete PITA ever since. I switch it off half the time now coz it's become a resource hog.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine AllenI thought the Resharper resource story had been improving? All of these tools seem to generate complaints though. I use Refactor! Pro. It's mainly OK, though it does have its moments. Difficult to distinguish between it and VS 2005's general sluggishness though.
Kevin
-
4.5 available yet? If it's beta is it stable?
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine Allen