any reason for VS2005 Pro for cf development?

[khorad]

I am trying to decide whether I need VS2005 Pro or if Standard is
sufficient.

It will be used SOLEY for Mobile Device development to interface with a
desktop app (VB6 + Access)

just looking at Microsoft's comparison chart:
http://lab.msdn.microsoft.com/vs2005/productinfo/productline/default.aspx

The main differences that jump out as possibly relevant are
1. User experience (streamlined vs full)
2. Deployment tools (click once vs yes)
3. remote debugging (I can still debug on a PPC without this, correct?)

I realize this could be asked in the visual studio group, but it seems like
a higher concentration of .NETcf experts here who might be able to answer
these questions and point out anything I missed ;-)

 

[Ginny Caughey [MVP]]

khorad,

Visual Studio 2003 Standard should work ok for Smart Device development, but
I don't know if any of the missing features compared with Pro would matter
to you. Do you have an option to purchase Standard and later upgrade if you
want to?

 

[khorad]

Visual Studio 2003 Standard should work ok for Smart Device development

I assume you meant 2005 ;-)

but I don't know if any of the missing features compared with Pro would
matter to you.

only if they affect Smart Device development, and just looking at the
comparison matrix it's hard to tell

(no SQL server or webservices or anything like that, just activesync and
possibly rapi)

Do you have an option to purchase Standard and later upgrade if you
want to?

nothing beyond whatever standard upgrade options MS might provide, that's
why I want to make sure I make the right decision in the first place.

The only other features that look tempting are all the code
profiling/testing/management tools, but you have to go all the way to team
edition for that, so I'm doubly leary of going to Pro as it would cost more
yet not offer any improvement over Standard and still not provide the extra
functionality of Team

PS do all those code profiling and unit testing tools work for with .NETcf?

 

[Ginny Caughey [MVP]]

Oops. Make that Visual Studio 2005 Standard.

Sorry for the typo,

 

[Ginny Caughey [MVP]]

No, the unit testing tools don't work with the Compact Framework. That would
indeed be nice though.

 

[Daniel Moth]

PS do all those code profiling and unit testing tools work for with

.NETcf?

No, for unit testing see this:
http://www.danielmoth.com/Blog/2005/05/compact-framework-unit-testing.html

Cheers
Daniel