Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Thu, 20 Jul 2006 03:10:48


OK, I'll admit it up front - I just don't get it.

Here's our previous VS2003 development model. Developers develop the WS
solution on their own workstations, using their own IIS web servers mapped
to the local devleopment folder. Project compiles to a subfolder .\bin. To
deploy, the asmx page and bin subfolder are copied to the production server.

So now I upgrade to VS2005. OK, so except for the name, everything is
changed. No more project file, codebehind pages are moved into a subfolder,
causing the conversion itself to hiccup. OK, I can get by that. But where
the hell is the binary file being built???

Here's my target path in the .sln file:

Release.AspNetCompiler.TargetPath = "C:\VBProjects\SRSDev\Source Code\WSL
Components\bin"

So I hit Build | Rebuild Solution:

Rebuild All started...
Rebuild All succeeded

But where's the output file??? The bin folder is empty!!!

Please help if you can. Thanks!!!

- Joe Geretz -
 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Thu, 20 Jul 2006 03:29:19

Additional info:

When I compile in batch from Visual Build Pro, I get the following error:

ASPNETCOMPILER : error ASPRUNTIME: The precompilation target directory
(C:\VBProjects\SRSDev\Source Code\WSL Components\bin\) cannot be in the same
tree as the source application directory (C:\VBProjects\SRSDev\Source
Code\WSL Components\).

Now presumably, this is the same error which is preventing the production of
the binary output from the interactive compile. You'd expect the interactive
compile to give the same feedback as the batch compile does! :-\

OK, so what's the deal here? Are they saying that with VS2005 we can't
structure the project so that the project folder is the same folder mapped
as the virtual folder for the web service? Why would they change this?
What's the new best practices? All I want to do is get this upgrade from
VS2003 to VS2005.

Fine, so I'm not going to fight this thing. I change the target path to
Release.AspNetCompiler.TargetPath = "..\WSL Precomp\SRSFreedom". OK, the
build succeeds, but what's this? It looks like the there's an entire replica
of my solution at the target location, including the application DLL's
(who's names have all changed by the way). So I'm really confused about
this. Is this where my web site is supposed to be mapped? If so, why to they
call this a 'precompilation taget directory'? (Talk about an oxymoron - is
this the target (implies the end point, or is this a pre-compilation
folder?) What is this all about?

<rant>
Why does Microsoft seem to have a vested interest in making this so !@#$^%#
difficult for its customers???!!! I mean do they want the developer audience
or don't they? I have other issues to wrestle with here and this $@%$^ isn't
helping matters!
</rant>

Anyway, if you can help me out with this, I'll be immensely grateful to you!

Thanks!

- Joe Geretz -

 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Thu, 20 Jul 2006 03:33:38

o the DLL for a Web Service is now called App_Code.dll? What's the sense in
this? How would I deploy two web service pages (.asmx) to the same web site,
if both of their DLL's are named App_Code.dll?

Thanks for your help,

- Joe Geretz 0


"Joseph Geretz" < XXXX@XXXXX.COM > wrote in message
news:%23O5$ XXXX@XXXXX.COM ...


 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Thu, 20 Jul 2006 03:51:03

http://www.yqcomputer.com/

Looks like the pain of upgrading is 'by design' :-\

"Be prepared to spend the better part of a day completing the entire
process."

What's wrong with Microsoft? I'm not saying that Microsoft doesn't have
legitimate issues in wanting to restructure, but don't they have a
responsibility to make this process as smooth as possible for their
customers??!!

:-\

- Joseph Geretz -
 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Jon Mille » Thu, 20 Jul 2006 04:51:27

I didn't have old projects to convert, so, I didn't have as painful
experience as you. I agree though that I like the way standard projects are
organized. I don't like the way projects are organized differently between
standard Windows application projects and Web projects.

Jon
 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by linhard » Thu, 20 Jul 2006 07:28:49

Try using Web Application Projects:

Introduction to Web Application Projects
http://www.yqcomputer.com/ #wapp_topic4

This allows you to transfer a project from VS2003 to VS2005 and
maintain the original organization. You have to install a couple extra
things, but once I did that my project compiled fine without
reorganization.

-Paul
 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Thu, 20 Jul 2006 13:06:10

i Paul,

Was your project a Web Application or a Web Services project?

Thanks,

- Joe Geretz -

< XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...


 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Jon Mille » Fri, 21 Jul 2006 01:41:21

aybe you should just wait until Orcas comes out. It will no doubt be
totally different with WCF, so, why bother with VS 2005. ;-)

Jon

"Joseph Geretz" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...


 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by linhard » Fri, 21 Jul 2006 01:55:53

y project was an ASP.NET Web Services Application (which is a template
installed when you install Web Applications Projects).

This solution really solves the problems created when they reorganized
where the assemblies are stored for web sites (and puts the dll back in
the bin directory).

I am struggling getting WSE 2.0 upgraded to 3.0 or getting it to work
with .NET 2.0, but in terms of the problems you're facing Web
Applications Projects is the way to go.

-Paul


Joseph Geretz wrote:

 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Fri, 21 Jul 2006 20:55:09

gt; I am struggling getting WSE 2.0 upgraded to 3.0 or getting it to work

Uh oh. But that's exactly what I'm trying to migrate - a WSE project which
transfers files via Web Services. You haven't been able to convert this?

So how do I specify that I'd like to use the Web Applications Project model,
rather than the standard Web Services model?

Thanks!

- Joe Geretz -

< XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...


 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by linhard » Sat, 22 Jul 2006 02:48:36

ust do the two installations specified for the Web Application Project
and then try to open your VS2003 project with VS2005 and it will
automatically prompt you to convert the project using WAP. I don't
recall the exact steps, but I remember it was straight forward.

Regarding WSE, my problem is I use Endpoints which don't seem to be
supported by WSE 3.0 which has changed the security model. Believe me
I'm frustrated too, but it's not really (entirely) Microsoft's fault
since it was the Oasis standards committee that updated the security
spec.

It seems that it is theoretically possible to run WSE 2.0 with
VS2005/.NET 2.0. On the client, I had to add the reference to
Microsoft.Web.Services2.dll explicitly (right-click on project in
solution manager). However, VS2005 doesn't know how to generate the
MyAppWse proxy for the web service. You can either use the WseWsdl.exe
tool (which I couldn't get to work) or generate the proxy in VS2003 and
then cut and paste it into your Reference.vb file to compile in VS2005.
I did manage to compile and execute, but I get a type initializer
error {"WSE032: There was an error loading the microsoft.web.services2
configuration section."} when the client tries to create an instance of
the wse web service. I was however able to get the VS2005/.NET 2.0/WSE
2.0 web service to work correctly with a VS2003/.NET 1.1/WSE 2.0
client.

I was hoping I could just quickly get WSE 2.0 working with .NET 2.0,
but since I'm stuck and since the compilation procedures are rather
cumbersome anyway. I figure I'm going to have to rewrite my
UserNameTokenManager base the WSE 3.0 example and break up my web
service into a couple web services to get around the endpoint issue.

-paul

Joseph Geretz wrote:

 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by linhard » Sat, 22 Jul 2006 08:56:28

oe,

Just to let you know that I succeeded in getting WSE 2.0 working with
VS2005/.NET 2.0. I had an error in my app.config file and it took me a
while to learn how to track it down from the cryptic error messages.

The two key points that I detail above are:
(1) use the Web Services Application template
(2) generate the MyServiceWse proxy in VS2003 and cut & paste it into
the Reference.vb file in your VS2005 application (or use the
WseWsdl.exe tool)

One other point is that the WSE 2.0 Settings Tool is not available in
VS2005 (although you can run it from the Start Menu). In the end, the
only change I made to the App.Config file was to specify a
soapExtensionTypes (which didn't seem to be needed with .NET 1.1).:

Good Luck,
-Paul

App.Config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<!-- configuration settings -->
<system.web>
<webServices>
<soapExtensionTypes>
<add type="Microsoft.Web.Services2.WebServicesExtension,
Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" priority="1" group="0" />
</soapExtensionTypes>
</webServices>
</system.web>
<microsoft.web.services2>
<diagnostics>
<detailedErrors enabled="false" />
<trace enabled="false" input="c:\traces\ClientInput.xml"
output="c:\traces\ClientOutput.xml" />
<policyTrace enabled="false" />
</diagnostics>
<security>
<!-- Time To Live: Wait up to 2 minutes for web service to
respond -->
<defaultTtlInSeconds>120</defaultTtlInSeconds>
<timeToleranceInSeconds>43200</timeToleranceInSeconds>
</security>
</microsoft.web.services2>
</configuration>

XXXX@XXXXX.COM wrote:

 
 
 

Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Post by Joseph Ger » Wed, 26 Jul 2006 07:07:40

hanks. I finally got around to this. Once I installed the Web Applications
Project model,

http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx

the upgrade went like a breeze!!!

Note to Microsoft: If it ain't broke - then don't fix it! Thanks for putting
it back to the way it was!

- Joe Geretz -

< XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...