VS 2010 - WTF?

ok so we all know the help system is major broke.

some other things i wish they had done better jobs on:

1) SQL Reporting service support - i still have to use VS 2005 to edit old sqlrs2005 reports, when they did vs2008 they did the new format and did not make the tools support the old format.

2) Smart Device support - now the only devices will be winphone 7 - hey i have a device to support so i have to use VS 2008 for that.

so i have to use 3 versions of visual studio ..... WTF?

while i might get the reports upgraded to 2008 i can't make the hardware of the CE handhelds go away....

with all the work on VS2010 it seems like they could have found a way to plug in the old report editor and the CE 5.xx and CE 6.xx device support ....

What happens if you change the target framework in Visual Studio to target a previous .NET version?

I know the reporting is an issue than won't go away, I have to regress to SQL 2005 for a client so your post is sending a shiver down my spine. In know they said side by side is not an issue, but it'd be nice to target all your previous projects without issue so I may have to wipe the cobwebs off my 2005 version

vesuvius said:

What happens if you change the target framework in Visual Studio to target a previous .NET version?

 

I know the reporting is an issue than won't go away, I have to regress to SQL 2005 for a client so your post is sending a shiver down my spine. In know they said side by side is not an issue, but it'd be nice to target all your previous projects without issue so I may have to wipe the cobwebs off my 2005 version

multi-target for the desktop works just fine.

they just did not put in any support at all for CE device projects.

the pre-luanch stuff left it up in the air and now i can see that they were not ready to talk about phone 7 and left it a blank spot.

but there are a *LOT* more than just phones out there.... go look at casio's business site they sell about 6 different devices for point of sale, wherehouse and inventory stuff.....

I have about 150-180 casio handheld units that are not even close to going away....

the phone can not do what the hadhelds do, totaly different kind of use case / features etc...

and a netbook or slate will not do it..... it has to be very much a small rugged device that has to do what the IT-3100 does.

been developing on them for 5 years, started with the IT-3000 and now the 3100 models.

heck i do not even try to run an emulator i just code and build and copy the cab file ....

as for SQL i think by end of the year i can move the customer to 2008 R2 servers - *if* things go right ... hoping to get them to make that move....

 about 60 or so reports to migrate if we do.

figuerres said:

vesuvius said:

*snip*

multi-target for the desktop works just fine.

 

they just did not put in any support at all for CE device projects.

 

the pre-luanch stuff left it up in the air and now i can see that they were not ready to talk about phone 7 and left it a blank spot.

 

but there are a *LOT* more than just phones out there.... go look at casio's business site they sell about 6 different devices for point of sale, wherehouse and inventory stuff.....

I have about 150-180 casio handheld units that are not even close to going away....

the phone can not do what the hadhelds do, totaly different kind of use case / features etc...

and a netbook or slate will not do it..... it has to be very much a small rugged device that has to do what the IT-3100 does.

 

been developing on them for 5 years, started with the IT-3000 and now the 3100 models.

heck i do not even try to run an emulator i just code and build and copy the cab file ....

 

as for SQL i think by end of the year i can move the customer to 2008 R2 servers - *if* things go right ... hoping to get them to make that move....

 about 60 or so reports to migrate if we do.

I expect Microsoft will continue to support VS2008 as long as there are OEMs using CE. Either that or they'll have to release a seperate SKU.

Wow, dropping CE support is something I didn't see coming. It doesn't affect me, but I know there are tons of devices out there that use it. I wonder what their reasoning was on that one.

So far, aside from the neat thread profiling and debugging tools, I don't see too many reasons to upgrade from VS2008.

spivonious said:

Wow, dropping CE support is something I didn't see coming. It doesn't affect me, but I know there are tons of devices out there that use it. I wonder what their reasoning was on that one.

 

So far, aside from the neat thread profiling and debugging tools, I don't see too many reasons to upgrade from VS2008.

Isn't this why they made the versions work side by side?  Some people still have to run VB6 you know

spivonious said:

Wow, dropping CE support is something I didn't see coming. It doesn't affect me, but I know there are tons of devices out there that use it. I wonder what their reasoning was on that one.

 

So far, aside from the neat thread profiling and debugging tools, I don't see too many reasons to upgrade from VS2008.

Visual Studio 2010 for me is a lovely place to be. If you are running it on Windows 7 and a decent setup, I would choose it anyday over 2008. The UML tools are a godsend (when you crash into a new job with a huge codebase) and the intellitrace, but the big thing for me is the parallel programming. I am writing a processor intense image processing application,and have been able to gain some substantial performance impovements. There are things like IObserver and IObservable that I have not even started to look at with regard to MVVM, and I will need to do some scripting possibly in C# with dynamic or maybe even F#.

I installed it immediately for the router Service in WCF that is another tremendous feature, worth the price for the upgrade itself, so I kinda like VS2010 - a lot really!

leeappdalecom said:

spivonious said:

*snip*

Isn't this why they made the versions work side by side?  Some people still have to run VB6 you know

I wouldn't consider VB6 related to .NET at all, but I do see your point.

spivonious said:

leeappdalecom said:

*snip*

I wouldn't consider VB6 related to .NET at all, but I do see your point.

If VB6 was good enough for Jesus Christ it should be good enough for a virtual machine. That's why I put each dev enviroment in its own VM. Plus, I find that I develop my own tool chains for each revision. It's nice to keep them isolated.

-Josh

spivonious said:

Wow, dropping CE support is something I didn't see coming. It doesn't affect me, but I know there are tons of devices out there that use it. I wonder what their reasoning was on that one.

 

So far, aside from the neat thread profiling and debugging tools, I don't see too many reasons to upgrade from VS2008.

To make things even more infuriating, if you have any test projects in VS2008, you are forced to upgrade them to .NET Framework 4.  In other words, they decided to not support multi-targeting for test projects!

Isn't that exciting?  You can't even test your code using the same framework version you'll be releasing it with...