NQPQ: Which versions of Visual Studio are acceptable for articles?
-
Yes, upgrade to 2010, but don't go so crazy as to convert to 2012 or 2013!
- I would love to change the world, but they won’t give me the source code.
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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!
-
Yes, upgrade to 2010, but don't go so crazy as to convert to 2012 or 2013!
- I would love to change the world, but they won’t give me the source code.
:doh: There is no likelihood of upgrading to a newer version of Visual Studio at this time. My question was about whether or not new articles written with VS 2008 are worth posting.
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
-
Yes, upgrade to 2010, but don't go so crazy as to convert to 2012 or 2013!
- I would love to change the world, but they won’t give me the source code.
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.
"Coming soon"
-
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
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
-
:doh: There is no likelihood of upgrading to a newer version of Visual Studio at this time. My question was about whether or not new articles written with VS 2008 are worth posting.
Gregory.Gadow wrote:
articles written with VS 2008
Which visual studio control are you using?. I can't seem to find an article writing control in the VS 2008 toolbox!
"Coming soon"
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
I hope to have it posted by next week.
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
Gregory.Gadow wrote:
Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
Absolutely worth doing. Post away! :thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
-
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 :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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.
-
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 :laugh:
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'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 :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
I use 2013/2012 - and it has a lot nice (and good) additions for web. But it didn't cost me a dime...
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
Quote:
Which versions of Visual Studio are acceptable for articles?
Every version that has users still using it. ie Every version.
-
Not Quite a Programming Question, so I'm asking in the forum that has the most eyes. If I should move it elsewhere, please let me know kindly. :^) I have an article I'd like to write out and post, about a database toolkit. I haven't done so because I still use Visual Studio 2008: our codebase is exclusively in VS 2008, it works well, and my company has seen no need to spend thousands of dollars to upgrade. Worth doing, or is VS 2008 too outdated for such an article to be taken seriously?
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
