@Microsoft
-
Again, it depends on how many of your clients live in the third world and can't get half decent internet access. .NET 3.0, the WPF part at least, was really buggy. Why not target a framework with fixed bugs ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
it depends on how many of your clients live in the third world
So, basically the majority of people who ask questions in Quick Answers. ;P The point is that there are valid scenarios where one might want to target .Net 3.0. Not that one should always do so when given the choice.
Christian Graus wrote:
Why not target a framework with fixed bugs ?
I've been telling people who use IE6 that for a while now... sometimes they just don't seem to listen. ;) It really depends on your target demographic. Some people don't want to spend the time for a lengthy install and others aren't able to perform an install due to funky IT policies. For any of my personal software, I use the latest and greatest. But that isn't always ideal for corporate software.
-
Yes. You are correct. 3.0 was released during the life of VS2005 to bring WPF etc. VS2008 was released with 3.5.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
This[^] could help you out for such matters. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
Create project in Visual Studio 2008, do not use Linq at all and code for three months, then try to Target .NET Framework 3.0...
Yes, been there, done that. And...?
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
I personally dislike that it adds that to new files. I rarely ever use it and it clutters up Intellisense (until I get annoyed enough to go and delete it from the top of the file). I wonder if the template for new files can be changed so that that using statement isn't part of it... that'd be nice.
Yes, by modifying the class.cs file in class.zip in the program files directory of whichever VS version. http://blogs.msdn.com/b/steve/archive/2007/04/10/changing-the-default-using-directives-in-visual-studio.aspx[^]
-
Yes, by modifying the class.cs file in class.zip in the program files directory of whichever VS version. http://blogs.msdn.com/b/steve/archive/2007/04/10/changing-the-default-using-directives-in-visual-studio.aspx[^]
I love you.
-
In that case, if you know you will not be using LINQ, target .NET 3.0 right from the start. Don't blame Microsoft for your lack of foresight.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
Henry Minute wrote:
Don't blame Microsoft for your lack of foresight.
WRONG. WHy do I have to make this decision in advance?
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
I love you.
-
Well, apparently.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
So, should I right click -> sort and delete in every code file in Solution or can I PowerCommands [^] to do that for me? Definitely agree with you on "difficult stuff this programming", though.
-
This[^] could help you out for such matters. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Nice link Luc! :thumbsup: Although I can't imagine what sort of anorak would have the time to aggregate such information. :laugh:
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
-
If it's just the using directive, do a search and replace? If it's just inconvenient having it by default I think there's a way to change the default usings. I've never done it though as it didn't look the simplest thing to do last time I looked into it (I wanted to have "using System.Diagnostics" included by default). My personal linq peeve is the people who insist on constantly "refactoring", replacing the foreach keyword with List.ForEach everywhere, which is slightly harder to read and debug imo, as well as leading to more conflicts when I'm trying to merge my actual changes in.
-
:-\
Predrag Tomasevic wrote:
Definitely agree with you on "difficult stuff this programming", though.
That's why it should be left to professional software engineers
Two heads are better than one.
I can't man... I as a manager must meet deadlines, and whenever I ask "professional software engineer" (I like to call them "programmer" instead) when it will be done, he replies something like: "When it's done". So, I've decided to take matters into my own hands... as numerous management books advised me - action before anything else!
-
I can't man... I as a manager must meet deadlines, and whenever I ask "professional software engineer" (I like to call them "programmer" instead) when it will be done, he replies something like: "When it's done". So, I've decided to take matters into my own hands... as numerous management books advised me - action before anything else!
Good engineers, will explain what's required to finish, it truly is hard to give a definite timescale as some problems or technical hurdles always appear down the line. So if your pressing somebody for a timescale as what steps are required to finish the jobs and a ballpark figure on have long each step will take. This is text book management that all companies use. They will take that information away and probably add/take a percentage on the timescale given. At the proposed step call the team/developer in and ask them if it complete and why not? Then adjust timescales accordingly. Breaking a project down into bite sized pieces is the only way to go, this is from my only person experience in the industry.
Two heads are better than one.