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 / ASP.NET / Web Services / January 2007

Tip: Looking for answers? Try searching our database.

Wse3 'Add web reference' Vista 64 bit

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Phil Lee - 13 Dec 2006 12:43 GMT
I have an existing WSE3 enabled web service which is now working fine on
Vista 64 bit.
My one remaining issue is that 'Update web reference' in VS2005 doesn't
generate a WSE enabled proxy.
It looks like the 'wsesettingsvs3.dll' isn't getting registered correctly.
Does anyone know how to get this working correctly?

If I run 'Update web reference' on my XP box I get this in reference.cs

   [System.CodeDom.Compiler.GeneratedCodeAttribute("System.Web.Services",
"2.0.50727.42")]
   [System.Diagnostics.DebuggerStepThroughAttribute()]
   [System.ComponentModel.DesignerCategoryAttribute("code")]
   [System.Web.Services.WebServiceBindingAttribute(Name="...",
Namespace="...")]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(DataResponse))]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(Query))]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(Request))]
   public partial class ServiceWSWse :
Microsoft.Web.Services3.WebServicesClientProtocol {

If I run it on Vista I get:

   /// <remarks/>
   [System.CodeDom.Compiler.GeneratedCodeAttribute("System.Web.Services",
"2.0.50727.312")]
   [System.Diagnostics.DebuggerStepThroughAttribute()]
   [System.ComponentModel.DesignerCategoryAttribute("code")]
   [System.Web.Services.WebServiceBindingAttribute(Name="...",
Namespace="...")]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(DataResponse))]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(Query))]
   [System.Xml.Serialization.XmlIncludeAttribute(typeof(Request))]
   public partial class ServiceWS :
System.Web.Services.Protocols.SoapHttpClientProtocol {

Regards
Phil Lee
James Hancock - 13 Dec 2006 18:01 GMT
Known bug. Hence why I've been begging for a SP1 of WSE 3.

This happens on all 64bit OSes.

Then there is the out of memory issues and StringBuilder Issues. And WSE 3
not encoding stuff correctly with reserved XML characters (0x0, etc.) when
WSE 2 did... lots of bugs!!!

>I have an existing WSE3 enabled web service which is now working fine on
>Vista 64 bit.
[quoted text clipped - 34 lines]
> Regards
> Phil Lee
Phil Lee - 14 Dec 2006 10:35 GMT
James,

I saw your previous post.  I thought another post wouldn't do any harm.
However seeing the 'is anybody from Microsoft reading this?' post above I
have reposted in the MS forum.

Regards,
Phil
> Known bug. Hence why I've been begging for a SP1 of WSE 3.
>
[quoted text clipped - 43 lines]
>> Regards
>> Phil Lee
Steven Cheng[MSFT] - 15 Dec 2006 04:13 GMT
Hi Phil,

I've checked the internal database and did found the bug entry about the
"WSE 3.0 proxy not generated on 64-bit Windows" issue. Here is the public
bug report link:

http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=211&FeedbackI
D=143745

Sorry for the inconvenience it brings.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
Phil Lee - 15 Dec 2006 10:00 GMT
Steven,

so can we expect a fix for this?  It can't be that difficult to fix.

Regards,
Phil Lee
> Hi Phil,
>
[quoted text clipped - 15 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Steven Cheng[MSFT] - 18 Dec 2006 08:40 GMT
Thanks for your followup Phil,

So far I haven't got any definite info about the public fix of the WSE 3
component for 64 bit machine.  Currently since this is an exiting issue, if
you do need a fix for you to work in the work environment, you can contact
CSS for a hotfix on this.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
James Hancock - 27 Dec 2006 01:16 GMT
Steven,
How about the out of memory errors with MTOM attachments > 30 megs?

> Thanks for your followup Phil,
>
[quoted text clipped - 12 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Phil Lee - 11 Jan 2007 12:23 GMT
Steven,

I contacted CSS and they wanted to know the hotfix id/reference.
Is there a hotfix for this issue and if so can I have the id?

Regards,
Phil Lee
> Thanks for your followup Phil,
>
[quoted text clipped - 12 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Steven Cheng[MSFT] - 12 Jan 2007 10:16 GMT
Hello Phil,

For the issue, there is no public documented hotfix from knowledge base
site. I used to locate this issue in our internal database. You need to
open an regular support incident with CSS product support team to deal with
this issue.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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

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.