Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / May 2006

Tip: Looking for answers? Try searching our database.

Version of VSDesigner in VS.NET 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Eric - 23 May 2006 21:30 GMT
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
Steven Cheng[MSFT] - 24 May 2006 09:41 GMT
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.

Signature

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

Steven Cheng[MSFT] - 25 May 2006 13:52 GMT
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.

Signature

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

Eric - 25 May 2006 21:12 GMT
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
Eric
Steven Cheng[MSFT] - 26 May 2006 02:48 GMT
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.

Signature

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


Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.