all groups > visual studio .net ide > may 2006 >
You're in the

visual studio .net ide

group:

Version of VSDesigner in VS.NET 2003


Version of VSDesigner in VS.NET 2003 Eric
5/23/2006 1:30:02 PM
visual studio .net ide:
Hi,

During updating a web reference I remarked a difference between two
autogenerated files (Reference.cs):

One contains:
This source code was auto-generated by Microsoft.VSDesigner, Version
1.1.4322.2032

The other:
This source code was auto-generated by Microsoft.VSDesigner, Version
1.1.4322.2300

There seems to be two different version of VS.NET 2003, but I have no idea
when or from which update this was updated. There exist no service pack, no?

Any clues?

Thanks
Eric
RE: Version of VSDesigner in VS.NET 2003 stcheng NO[at]SPAM online.microsoft.com
5/24/2006 12:00:00 AM
Hello Eric,

Welcome to the MSDN newsgroup.

As for the version number in webservice proxy code generated by Visual
Studio IDE(like below), it is actually the version of the current .net
framework runtime.

===========
This source code was auto-generated by Microsoft.VSDesigner, Version
1.1.4322.2032
===========

For example, the above version (1.1.4322.2032) indicates the current .net
framework is version 1.1. The number "4322" is the build number, and
number "2032" is the revision nunmber. The revision number may change when
the .net framework is upgrated or any service pack is installed. In your
case, the "2032" is specific to .net framework 1.1 which has applied
service pack 1 while the "2300" is specific to .net framework 1.1 which has
applied windows 2003 service pack1.

In addition, here is a kb article which lists the version info of .net
framework and its service packs:

#How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)



RE: Version of VSDesigner in VS.NET 2003 stcheng NO[at]SPAM online.microsoft.com
5/25/2006 12:52:40 PM
Hi Eric,

Does the info in my last reply helps you a little? If there is still
anything else we can help, please feel free to post here.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
RE: Version of VSDesigner in VS.NET 2003 Eric
5/25/2006 1:12:01 PM
Hi Steven,

Thanks for answering.

Yes, I think now it's clearer.
I have used XP and Win2003 for updating the Webservice reference.

But does this mean that I should use Win2003 for developing? It seems more
'advanced'.
Or can I assume that .NET Framework on XP and Win2003 have the same 'state'?

Thanks
RE: Version of VSDesigner in VS.NET 2003 stcheng NO[at]SPAM online.microsoft.com
5/26/2006 1:48:46 AM
Thanks for your further followup Eric,

Of course the different "revision" number won't matter in your case
because it just indicate the runtime version of the VSDesigner assemby and
this assembly just help generate the source code file. And the source code
file should be working well among all those changes(main version or applied
SPx).

Also, even you're developing with both version, the .net framework is able
to work well between them since there is internal version policy that can
make the .net CLR think such small change (revision number) be compatible.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
AddThis Social Bookmark Button