|
If i had to upgrade from VS 2008 now, i would go straight to VS 2013. The only upgrade worthy doing is one that skips VS 2012.
|
|
|
|
|
It the article is well done I can't see a reason not to publish it - for sure VS 2008 not a reason.
If you publish code from 2008 will be no problem to open it in any VS - so go for it!
|
|
|
|
|
Personally
There are articles on CP that are written with .net 1.1
I have recently referenced an article that was in dot net 2.0 and applied the techniques to a dot net 4.0 application.
So yes if the technique is still relevant I would write the article.
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Agreed - I answered a QA question yesterday / today that was .NET 2.0, so there are still developers who are limited to that: VS2005 IIRC.
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
When I went to VS 2005, my code wouldn't compile because it used an outdated delegate mode that worked great in 2004. Of course this was from a class using 500 MH CPUs and I had no clue about VS levels while taking the class. I think this is the kind of thing that might upset some readers and what the original question was about. Of course I say, let the readers squawk. (Well it works on MY machine!)
|
|
|
|
|
Gregory.Gadow wrote: Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
I've upgraded projects from 2008 to 2012 without issues, and I don't think readers will have issues with that either. I suspect that, as I do, we still have VS2008 lingering on our systems.
So, I think that the VS version of the solution is minor compared to the topic and quality of the code and article. Hope that helps.
Marc
|
|
|
|
|
If the points and concepts of the article can pertain to newer versions of Visual Studio, then why not just go ahead and write the article. Even if it is VS 2008 specific, it might still be found interesting or useful by the CP Community anyways. So in short, go for it!
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|
|
Worth doing - I answered a QA question yesterday / today that was .NET 2.0, so there are still developers who are limited to that: VS2005 IIRC.
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
I hope to have it posted by next week.
|
|
|
|
|
Gregory.Gadow wrote: Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
Absolutely worth doing. Post away! 
/ravi
|
|
|
|
|
You can get the free 2013 Express edition. That's what I'm doing when I post code for an article.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Like many others have said, I don't think it is a problem if you use VS2008. As a matter of fact, I would prefer you don't post a VS2013 solution since I am not yet set up for that (and I assume I am not the only one still stuck on VS2010).
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
I'm using it - but by choice. VS2012 got too many complaints (and I didn't need it) and I don't see 2013 as a big enough step version to want to be another paying MS beta tester 
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
I would like to upgrade and take a stab at some WP8 development, but first I have to upgrade my main system from WinXP...
I have been putting that off for several reasons, but my plan is to buy an SSD drive and install Win8.1 on it, leaving my old drives in the system so I can go back to XP in case I need to do something I can't do in Win8.1.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
I use 2013/2012 - and it has a lot nice (and good) additions for web. But it didn't cost me a dime...
|
|
|
|
|
VS2013 is actually very stable, and is much faster than VS2010 and VS2012. It has quite a few cool features (notifications of updates and other things being one), and opens most VS solutions out there.
The only real issues I have had are the weird line count for an error (posted in the Weird and the Wonderful), and the Git integration bug that causes repository creation to fail if another repository was deleted in the same VS instance. E.g. I have a test project in an instance of VS, close it, delete the folder, and try to use the same instance of VS to create a new project. Most of the time it will fail, sometimes it won't show an error, and sometimes it will work as expected.
Getting information off the Internet is like taking a drink from a fire hydrant.
- Mitchell Kapor
|
|
|
|
|
Your choice (?) of development environment should have no bearing on the content of the article. (I try to avoid Visual Studio whenever I can.) The reader shouldn't care what tools you use; only the code and techniques matter.
On the other hand, you should aim to support the oldest version of the framework as comfortable no matter how you develop.
|
|
|
|
|
Quote: Which versions of Visual Studio are acceptable for articles?
Every version that has users still using it.
ie Every version.
|
|
|
|
|
Articles written with VS 2008 are worth posting. VS 2010, 2012 and 2013 offer a compliant converting mechanism.
Veni, vidi, caecus | Everything summarizes to Assembly code
|
|
|
|
|
Answering your QUESTION, I would definitely read an article for software written in VS2008, or even 2005.
If you want to use the CODE, it should be easy to port as all previous versions of .NET will be compatible.
People who worry about upgrading projects are obviously lazy or they can't programme for toffee.
People who are telling you which version to upgrade to cannot read. 
Me? I'm thinking of submitting an article written in .Net 4(Mono/VS) about a tiny encryption pad I wrote for sport a few years ago. It will be bare code and people can make it compatible with whatever.
|
|
|
|
|
I still use 2008 mostly because it works for what I need and is compatible with Windows XP and up. The fact that I can't justify the expense to the management for an upgrade 'it works, why change it?' attitude (I'm the only one in the company who does Windows programming). The chances are the bit you reference hasn't had changes or the interface hasn't changed. I for one haven't had to use a database in anger, but it's looking like I might have to soon. Go For It  
|
|
|
|
|
Go ahead.
It's not like the same principles will suddenly not apply.
My company was still using VS 2008 for the project I work on until a few months ago.
|
|
|
|
|
All of my articles were written using a development environment that included only VS2008. I find nothing in later versions of VS that I cannot program in VS2008. Also, writing an article in the later VS versions effectively limits your article's audience. Although it is possible to convert down to VS2008, why ask a reader to do so?
VS2008 is my choice.
Gus Gustafson
|
|
|
|
|
|
No, I don't think it's outdated at all. It's a solid platform. I've standardized all my development on it with attendant tools and I, too, find the idea of "upgrading" unpalatable. I write to the desktop and have a massive library I've developed over the years there's no reason, at all, to consider an upgrade. My code runs on everything from XP to Windows 8 desktop with no issues. Upgrading would be a colossal waste of money.
IMHO, just hunker down and stick with it unless you find something you REALLY need to do but is only offered in later versions. I can see you're doing similar work with your database toolkit. I've done same. Why retool and/or re-invent the wheel at this stage?
Write your article. I suspect there are many people that would use it. Besides, as someone else has already said: if you're using a later version the techniques won't change.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
