[quoted text, click to view] "Tim T." wrote:
> OK, I've looked and looked in the newsgroups, Microsoft and Google but have
> found no real help in determining if Visual Studio 2003 Professional SE is
> EXACTLY the same as Professional, just with Server 2003 and SQL 2000
> Developer Ed. added on. When Microsoft says that it "has all of the
> functionality of Professional", I get weary. Why is SE priced ~$300 cheaper
> than Professional? Something doesn't seem right.
>
> I currently have Standard (VB.NET and C#) and I am unable to create Class
> Library projects in VB.NET. I need Professional but I don't know if I should
> get Professional SE or not. The $300 difference is freaking me out.
>
> Can anyone tell me if Professional SE is EXACTLY the same as Professional?
> I don't want to buy SE and find out that it can't do the same things as
> Professional.
>
Regarding the steep discounting of VS2003 Professional SE, I think the
answer lies in timing, i.e. it is being offered at the very end of VS 2003's
life cycle and therefore MS is using the discount as an inducement to
purchase an item that is by all measures already outdated. This raises an
even more important question IMO which is if I purchase SE today and VS2005
goes live tomorrow what will be MS's upgrade policy for me and others like
me? Will it be free or will I be forced to pay again to upgrade? If I am
forced to pay again then the savings I realize on SE isn't real as it will be
made up by what I will have to pay for the 2005 upgrade.
Because I haven't been able to find an answer to this question I therefore
haven't made the move to the SE release. I'm a consultant and every penny I
spend on development tools comes out of my own pocket. If MS published its
upgrade policy from VS 2003 SE to VS 2005 Professional then perhaps, if the
policy were reasonable, I'd make the move... Hint hint hint, MS.
I'm rather a big fan of MS development products, especially because they
allow me to sell my services to a large audience who use them but I am not
willing to gamble on this deal just yet.
PS
I also develop custom ASP server controls and though there is no project
template for them in VWD 2005 and the standard 2003 editions I create them
using batch files to build them. I hope MS realizes that building custom ASP
server controls isn't an advanced feature but rather a necessarry feature for
many intranet and public web sites as it enforces encapsulation, abstraction,
and reuse in ways that user controls are just not capable of... another hint,
MS.