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 / August 2005

Tip: Looking for answers? Try searching our database.

WSE 3.0 CTP No Configuration Tool

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Daniel Danilin - 07 Jun 2005 17:35 GMT
I have just installed WSE 3.0 CTP (Custom installation with all selected). I
can't find WSE Config Tool in VS 2005 Beta2 and VS 2003. Is it known issue
or a bug?

P.S. I have German Windows version.
Reply to this Message
William Stacey [MVP] - 08 Jun 2005 03:03 GMT
There is two packages, the runtime and the full install with the doco and VS
tool, etc.  The msi is 10MB, not the 1MB runtime.  This confused me as well.

Signature

William Stacey [MVP]

>I have just installed WSE 3.0 CTP (Custom installation with all selected).
>I can't find WSE Config Tool in VS 2005 Beta2 and VS 2003. Is it known
>issue or a bug?
>
> P.S. I have German Windows version.
Reply to this Message
Daniel Danilin - 08 Jun 2005 11:13 GMT
I have installed 10Mb msi with Docs and VS tools. I can start it from
Startmenu, but there is no Tool in VS 2005 and VS 2003.

> There is two packages, the runtime and the full install with the doco and
> VS tool, etc.  The msi is 10MB, not the 1MB runtime.  This confused me as
[quoted text clipped - 5 lines]
>>
>> P.S. I have German Windows version.
Reply to this Message
Fernando - 08 Jun 2005 17:57 GMT
I have the same problem I install all the WSE3.0 and when I open a proyect of
the started kit examples the option WSE3.0 Doesn't appear in the contextual
menu after a rigth click. My OS is Windows xp profesional with sp2 in spanish
Reply to this Message
William Stacey [MVP] - 08 Jun 2005 18:22 GMT
There was a dialog box during install to Select "Developer" install to
install VS tool, etc.  Remove and install again and make sure you select
that option.

Signature

William Stacey [MVP]

>I have installed 10Mb msi with Docs and VS tools. I can start it from
>Startmenu, but there is no Tool in VS 2005 and VS 2003.
[quoted text clipped - 8 lines]
>>>
>>> P.S. I have German Windows version.
Reply to this Message
Daniel Danilin - 08 Jun 2005 22:25 GMT
I have installed with Developer option and with Visual Studio Developer
option. There is no config tool in VS2005.
It's a bug.

> There was a dialog box during install to Select "Developer" install to
> install VS tool, etc.  Remove and install again and make sure you select
[quoted text clipped - 12 lines]
>>>>
>>>> P.S. I have German Windows version.
Reply to this Message
William Stacey [MVP] - 09 Jun 2005 01:04 GMT
When I right click on the Project (not the solution) I see "WSE Settings
3.0...".  You don't see that?  Maybe some install order or build issue.

Signature

William Stacey [MVP]

>I have installed with Developer option and with Visual Studio Developer
>option. There is no config tool in VS2005.
[quoted text clipped - 16 lines]
>>>>>
>>>>> P.S. I have German Windows version.
Reply to this Message
Daniel Danilin - 09 Jun 2005 20:26 GMT
Exactly, right click on the Project and nothing.
WSE 3 is not suppose to be installed on non english windows.

> When I right click on the Project (not the solution) I see "WSE Settings
> 3.0...".  You don't see that?  Maybe some install order or build issue.
[quoted text clipped - 19 lines]
>>>>>>
>>>>>> P.S. I have German Windows version.
Reply to this Message
Mark Fussell [MSFT] - 23 Jun 2005 03:05 GMT
There is certainly a bug in the installation of the WSE Add-in which is in
VS Beta 2 release currently. We are looking into this.
You have to ensure that VS is not running when you install WSE 3.0
otherwise the add-in will certainly fail.
If this does not install, using the standalone configuration tool is the
best approach for now. You only get convenience by having the context menu.

Thanks,
Mark Fussell
WSE Program Manager

--------------------
From: "Daniel Danilin" <nesher.hh@web.de>
References: <e4v0N83aFHA.3100@TK2MSFTNGP14.phx.gbl>
<#6V0u58aFHA.3736@TK2MSFTNGP15.phx.gbl>
<enRRbLBbFHA.1040@TK2MSFTNGP10.phx.gbl>
<#iNKW7EbFHA.228@TK2MSFTNGP12.phx.gbl>
<e#W6vDHbFHA.612@TK2MSFTNGP12.phx.gbl>
<u9R55bIbFHA.2688@TK2MSFTNGP14.phx.gbl>
Subject: Re: WSE 3.0 CTP No Configuration Tool
Date: Thu, 9 Jun 2005 21:26:51 +0200
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Response
Message-ID: <O2qJ6kSbFHA.3328@TK2MSFTNGP09.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
NNTP-Posting-Host: c145060.adsl.hansenet.de 213.39.145.60
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:4277
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements

Exactly, right click on the Project and nothing.
WSE 3 is not suppose to be installed on non english windows.

"William Stacey [MVP]" <staceywREMOVE@mvps.org> schrieb im Newsbeitrag
news:u9R55bIbFHA.2688@TK2MSFTNGP14.phx.gbl...
> When I right click on the Project (not the solution) I see "WSE Settings
> 3.0...".  You don't see that?  Maybe some install order or build issue.
[quoted text clipped - 23 lines]
>>>>>>
>>>>>> P.S. I have German Windows version.

Signature

Mark Fussell - WSE Program Manager
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Reply to this Message
Pantano Antonio - 21 Jul 2005 23:48 GMT
I think using standalone configurations tools doesn't configure the proxy
class and  doesn't import the namespace.
I solved the problem in this way.
Search in you C:\Documents and Settings\All Users\Application
data\Microsoft\MSEnvShared\Addins
here you'll find a file vsesettingVS3.addin.
Copy and paste it in a new folder you create in C (e.g. c:\VSAddins\)
Open VS2005 Beta 2 and go in the menu -Tools-Options..
In the windows that appear select Environment->Add-is/macros security node
in the tree and than the Add button. Point the folder where you pasted the
wsesettingvs3.addin file and click OK.
VS say you that the changes will have effect at next time you start VS2005.
Close it and open again. Now open or create a project and right click on it
in solution explorer.

That's all.
Ciao. Pantano Antonio - Italy.

> There is certainly a bug in the installation of the WSE Add-in which is in
> VS Beta 2 release currently. We are looking into this.
[quoted text clipped - 6 lines]
> Mark Fussell
> WSE Program Manager
Reply to this Message
Naresh Bhatia - 22 Aug 2005 03:03 GMT
I tried the suggested procedure below. Still the addin does not show in VS
2005. Is there a new drop expected that fixes this problem?

> I think using standalone configurations tools doesn't configure the proxy
> class and  doesn't import the namespace.
[quoted text clipped - 24 lines]
> > Mark Fussell
> > WSE Program Manager
Reply to this Message

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.