2003 v. 2005 studio - need some help, please.

  • Thread starter Thread starter matthewtec
  • Start date Start date
M

matthewtec

I realize there are probably many discussions on these two... whether to get
now or wait or yadda yadda yadda.

My question is that I can continuing training on visual studio.net 2003, and
continue to learn and be able to be an experienced programmer.

And I fully realize that I'd obviously be missing out on some functionality.
However, in the actual phase of getting a job, does anyone have any thoughts
that would suggest I would get turned down my most people if I haven't used
2005 / though proficient in 2003.

Obviously the reason is money... I have 2003. I'm on the broke side, and I
can currently study fine now.

I just don't want to get to every job offer and be told that no matter how
much and how efficient I am and how elegant my code is, that I can't be
given a job because I haven't been exposed to 2005?



I realize these are sometimes throw away questions when they come in, but
this is very important for me, and I would appreciate your honesty and
candor.

Thank you so very much.
 
matthewtec said:
I realize there are probably many discussions on these two... whether to
get now or wait or yadda yadda yadda.

My question is that I can continuing training on visual studio.net 2003,
and continue to learn and be able to be an experienced programmer.

And I fully realize that I'd obviously be missing out on some
functionality. However, in the actual phase of getting a job, does anyone
have any thoughts that would suggest I would get turned down my most
people if I haven't used 2005 / though proficient in 2003.

Obviously the reason is money... I have 2003. I'm on the broke side, and
I can currently study fine now.

I just don't want to get to every job offer and be told that no matter how
much and how efficient I am and how elegant my code is, that I can't be
given a job because I haven't been exposed to 2005?



I realize these are sometimes throw away questions when they come in, but
this is very important for me, and I would appreciate your honesty and
candor.

Thank you so very much.
Click to expand...
In my opinion, you will find that lack of VS 2005 exposure/experience will
become more of a problem as time goes by. If you were seeking a job right
now, demonstrated proficiency with .NET Framework 1.1 and VS 2003 should be
OK. Six months from now? I'd predict more turndowns.
There is a free way to get some exposure to the new IDE and .NET 2.0.
Download and work with the free Express editions:

http://msdn.microsoft.com/vstudio/express/
 
That was sort of my thinking, but I just wanted to make sure I wasn't
completely off my rocker in that thought. If it turns out jobs are hard to
find because I know 2003 [1.1] vs. 2005 [2.0], we'll do what we have to.
But for now, there's the whole finite amount of money to get the best
training I can.

I appreciate your help.

Matt
 
While VS2005 wasn't the knock-my-socks-off upgrade I was expecting, it does
*simplify* a lot of things that were overly complex in V2003... so it would
behoove anyone to jump onboard VS2005 rather than fighting to get VS2003 to
do certain things. For instance, DataBinding is practically perfected in
VS2005 with the BindingManager control (which was sorta available in VS2003
but as a weird hidden and confusing object property of the form). The
DataAdapter has gotten a new wrapper and tied to a Dataset a la VB.Classic
in a new tool called the TableAdapter (a bad idea in my book... but good for
simple 2-tiered RAD applications). The layout panel controls that provide
beautiful control sizing and overflow wrapping make life sooooo much easier.
And, let's not forget the fantastic new DataGridView.

You could spend days (weeks?) trying to figure out how to get the old VS2003
DataGrid to work well.... or you can use VS2005.

--
-C. Moya
www.cmoya.com
matthewtec said:
That was sort of my thinking, but I just wanted to make sure I wasn't
completely off my rocker in that thought. If it turns out jobs are hard
to find because I know 2003 [1.1] vs. 2005 [2.0], we'll do what we have
to. But for now, there's the whole finite amount of money to get the best
training I can.

I appreciate your help.

Matt
Click to expand...
 
Thanks... I appreciate that POV as well. And yes, my life would be much
simpler with the DataGridView. I really want to try that out and use it.

[Granted, my life would be much simpler if I had the 750 clams to buy it].

I will keep that in mind and see what I can do about that.
Thanks!


CMM said:
While VS2005 wasn't the knock-my-socks-off upgrade I was expecting, it
does *simplify* a lot of things that were overly complex in V2003... so it
would behoove anyone to jump onboard VS2005 rather than fighting to get
VS2003 to do certain things. For instance, DataBinding is practically
perfected in VS2005 with the BindingManager control (which was sorta
available in VS2003 but as a weird hidden and confusing object property of
the form). The DataAdapter has gotten a new wrapper and tied to a Dataset
a la VB.Classic in a new tool called the TableAdapter (a bad idea in my
book... but good for simple 2-tiered RAD applications). The layout panel
controls that provide beautiful control sizing and overflow wrapping make
life sooooo much easier. And, let's not forget the fantastic new
DataGridView.

You could spend days (weeks?) trying to figure out how to get the old
VS2003 DataGrid to work well.... or you can use VS2005.

--
-C. Moya
www.cmoya.com
matthewtec said:
That was sort of my thinking, but I just wanted to make sure I wasn't
completely off my rocker in that thought. If it turns out jobs are hard
to find because I know 2003 [1.1] vs. 2005 [2.0], we'll do what we have
to. But for now, there's the whole finite amount of money to get the best
training I can.

I appreciate your help.

Matt


pvdg42 said:
I realize there are probably many discussions on these two... whether to
get now or wait or yadda yadda yadda.

My question is that I can continuing training on visual studio.net
2003, and continue to learn and be able to be an experienced
programmer.

And I fully realize that I'd obviously be missing out on some
functionality. However, in the actual phase of getting a job, does
anyone have any thoughts that would suggest I would get turned down my
most people if I haven't used 2005 / though proficient in 2003.

Obviously the reason is money... I have 2003. I'm on the broke side,
and I can currently study fine now.

I just don't want to get to every job offer and be told that no matter
how much and how efficient I am and how elegant my code is, that I
can't be given a job because I haven't been exposed to 2005?



I realize these are sometimes throw away questions when they come in,
but this is very important for me, and I would appreciate your honesty
and candor.

Thank you so very much.

In my opinion, you will find that lack of VS 2005 exposure/experience
will become more of a problem as time goes by. If you were seeking a job
right now, demonstrated proficiency with .NET Framework 1.1 and VS 2003
should be OK. Six months from now? I'd predict more turndowns.
There is a free way to get some exposure to the new IDE and .NET 2.0.
Download and work with the free Express editions:

http://msdn.microsoft.com/vstudio/express/
Click to expand...
Click to expand...
Click to expand...
 
To reiterate what the other posters wrote - just download the free
version of 2005. That's what I did -- I'm very glad I did now. There's
many issues with VS2003 and .Net 1.1 that are now resolved or improved
so better to put your time to use learning VS2005 and .NET 2.0 than
learning and developing workarounds that are redundant.

Plus -- the deeper you go and more intimate you become with VS2003 the
more difficult (I suspect) you'll find the transition to VS2005 because
you'll be to entrenched with the VS2003 way of working.

That's my 2c.
Thanks... I appreciate that POV as well. And yes, my life would be much
simpler with the DataGridView. I really want to try that out and use it.

[Granted, my life would be much simpler if I had the 750 clams to buy it].

I will keep that in mind and see what I can do about that.
Thanks!


CMM said:
While VS2005 wasn't the knock-my-socks-off upgrade I was expecting, it
does *simplify* a lot of things that were overly complex in V2003... so it
would behoove anyone to jump onboard VS2005 rather than fighting to get
VS2003 to do certain things. For instance, DataBinding is practically
perfected in VS2005 with the BindingManager control (which was sorta
available in VS2003 but as a weird hidden and confusing object property of
the form). The DataAdapter has gotten a new wrapper and tied to a Dataset
a la VB.Classic in a new tool called the TableAdapter (a bad idea in my
book... but good for simple 2-tiered RAD applications). The layout panel
controls that provide beautiful control sizing and overflow wrapping make
life sooooo much easier. And, let's not forget the fantastic new
DataGridView.

You could spend days (weeks?) trying to figure out how to get the old
VS2003 DataGrid to work well.... or you can use VS2005.

--
-C. Moya
www.cmoya.com
matthewtec said:
That was sort of my thinking, but I just wanted to make sure I wasn't
completely off my rocker in that thought. If it turns out jobs are hard
to find because I know 2003 [1.1] vs. 2005 [2.0], we'll do what we have
to. But for now, there's the whole finite amount of money to get the best
training I can.

I appreciate your help.

Matt


I realize there are probably many discussions on these two... whether to
get now or wait or yadda yadda yadda.

My question is that I can continuing training on visual studio.net
2003, and continue to learn and be able to be an experienced
programmer.

And I fully realize that I'd obviously be missing out on some
functionality. However, in the actual phase of getting a job, does
anyone have any thoughts that would suggest I would get turned down my
most people if I haven't used 2005 / though proficient in 2003.

Obviously the reason is money... I have 2003. I'm on the broke side,
and I can currently study fine now.

I just don't want to get to every job offer and be told that no matter
how much and how efficient I am and how elegant my code is, that I
can't be given a job because I haven't been exposed to 2005?



I realize these are sometimes throw away questions when they come in,
but this is very important for me, and I would appreciate your honesty
and candor.

Thank you so very much.

In my opinion, you will find that lack of VS 2005 exposure/experience
will become more of a problem as time goes by. If you were seeking a job
right now, demonstrated proficiency with .NET Framework 1.1 and VS 2003
should be OK. Six months from now? I'd predict more turndowns.
There is a free way to get some exposure to the new IDE and .NET 2.0.
Download and work with the free Express editions:

http://msdn.microsoft.com/vstudio/express/
Click to expand...
Click to expand...
Click to expand...
 
Back
Top