NQPQ: Which versions of Visual Studio are acceptable for articles?
-
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
-
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
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
-
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?
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.
-
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 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 :) :-D
-
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?
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
-
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?
DbToolbox: Utilities for data access and management[^] In case anyone still cares :zzz:
-
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"
