By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,432 Members | 790 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,432 IT Pros & Developers. It's quick & easy.

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

P: n/a
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 -
Jul 18 '06 #1
Share this Question
Share on Google+
15 Replies


P: n/a
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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -


Jul 18 '06 #2

P: n/a
So 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" <jg*****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
>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 -



Jul 18 '06 #3

P: n/a
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -


Jul 18 '06 #4

P: n/a
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
>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 -



Jul 18 '06 #5

P: n/a
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -

Jul 18 '06 #6

P: n/a
Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
>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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -


Jul 19 '06 #7

P: n/a
Maybe 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" <jg*****@nospam.comwrote in message
news:e9**************@TK2MSFTNGP05.phx.gbl...
Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
>Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
>>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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -



Jul 19 '06 #8

P: n/a
My 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:
Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -
Jul 19 '06 #9

P: n/a
Joe,

My web service project doesn't even have a bin folder. Did you have to add
one to the project?

Also, with the dll being called App_Code.dll, I'm guessing you distribute
the App_Code.dll and the asmx to the web server?

I feel your frustration!

Mark
"Joseph Geretz" wrote:
So 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" <jg*****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -



Jul 19 '06 #10

P: n/a
Visual Studio 2005 Web Application Projects
http://msdn.microsoft.com/asp.net/re...p/default.aspx

"Web Application Projects provide a companion web project model that
can be used as an alternative to the built-in Web Site Project in
Visual Studio 2005. This new model is ideal for web site developers who
are converting a Visual Studio .Net 2003 web project to Visual Studio
2005. (Released May 8, 2006)"

"All code files within the project are compiled into a single assembly
that is built and persisted in the \bin directory on each compile. "

"Because the Web Application Project model uses the same conceptual
semantics as the Visual Studio .NET 2003 web project model, it can make
migrating projects much easier-minimizing code changes."

-Paul

watte wrote:
Joe,

My web service project doesn't even have a bin folder. Did you have to add
one to the project?

Also, with the dll being called App_Code.dll, I'm guessing you distribute
the App_Code.dll and the asmx to the web server?

I feel your frustration!

Mark
"Joseph Geretz" wrote:
So 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" <jg*****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
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 -
>
"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
>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 -
>>
>>
>
>
Jul 19 '06 #11

P: n/a
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.
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 -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
My 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:
>Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googleg roups.com...
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -



Jul 20 '06 #12

P: n/a
Also, with the dll being called App_Code.dll, I'm guessing you distribute
the App_Code.dll and the asmx to the web server?
Yes. Since every Web Service now produces DLL's named App_Code.dll, how do I
deploy multiple web service pages to the same site? Who dreams this stuff
up? We're back to the days of Henry Ford - 'you can have any color, as long
as it's black'. You can name your output whatever you want, as long as it's
named App_Code.dll. :-\
I feel your frustration!
Yeah, me too!!! ;-)

Thanks,

- Joe Geretz -

"watte" <wa***@discussions.microsoft.comwrote in message
news:9D**********************************@microsof t.com...
Joe,

My web service project doesn't even have a bin folder. Did you have to
add
one to the project?

Also, with the dll being called App_Code.dll, I'm guessing you distribute
the App_Code.dll and the asmx to the web server?

I feel your frustration!

Mark
"Joseph Geretz" wrote:
>So 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" <jg*****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -




Jul 20 '06 #13

P: n/a
Just 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:
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.

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 -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
My 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:
Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -

Jul 20 '06 #14

P: n/a
Joe,

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.WebSer vicesConfiguration,
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>

li******@aol.com wrote:
Just 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:
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.
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 -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
My 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:
>Hi Paul,
>>
>Was your project a Web Application or a Web Services project?
>>
>Thanks,
>>
>- Joe Geretz -
>>
><li******@aol.comwrote in message
>news:11**********************@i42g2000cwa.googleg roups.com...
Try using Web Application Projects:
>
Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
>
>
Jon Miller wrote:
>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
>>
>"Joseph Geretz" <jg*****@nospam.comwrote in message
>news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp
>
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 -
>
"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
>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 -
>>
>>
>
>
>
>
Jul 20 '06 #15

P: n/a
Thanks. I finally got around to this. Once I installed the Web Applications
Project model,

http://msdn.microsoft.com/asp.net/re...p/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 -

<li******@aol.comwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
Joe,

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.WebSer vicesConfiguration,
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>

li******@aol.com wrote:
>Just 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:
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.

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 -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
My 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:
Hi Paul,

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

Thanks,

- Joe Geretz -

<li******@aol.comwrote in message
news:11**********************@i42g2000cwa.googleg roups.com...
Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/de...sp#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
Jon Miller wrote:
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

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
http://msdn.microsoft.com/asp.net/re...ojectsvs05.asp

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 -

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:OS**************@TK2MSFTNGP05.phx.gbl...
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 -


Jul 24 '06 #16

This discussion thread is closed

Replies have been disabled for this discussion.