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

Debug and release webservice projects

P: n/a
Hello,

In VS2003, I used to have two solutions - a debug and release solution.

Each solution had a webservice project and several other class library
projects. The webservice project referenced all the other class library
projects (i.e. so that it used the dll created when those other projects
were built).

The debug solution was configured so that all the projects in it had debug
as their active configuration, and the release project was configured so
that all the projects in it had release as their active project.

This meant that when the webservice project in the debug solution was built,
it would use debug dlls, and when the webservice project in the release
solution was built, it would use release dlls.

OK so far? Good.

Now with VS2005, things have changed.

There seems no longer to be the concept of the webservice project. Instead,
you add your site directly to the solution. And this is causing me problems.

The question is - what configuration do I adopt for the single site that I
now have?

If I add the site to my debug solution, then it will reference debug
projects and use debug dlls.

On the other hand, if I add the site to my release solution, then it will
reference release projects and use release dlls.

I was thinking that I could create two separate sites for each of the
solutions, but I don't want to have to start duplicating all the source *.vb
files for each project.

Any suggestion will be gratefully received.

Regards,

--
Akin

aknak at aksoto dot idps dot co dot uk
May 18 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Epetruk" <no****@blackhole.com> wrote in message
news:4d*************@individual.net...
Hello,
There seems no longer to be the concept of the webservice project.
Instead,
you add your site directly to the solution. And this is causing me
problems.

The question is - what configuration do I adopt for the single site that I
now have?


Akin,

I do not know how to solve this terribly stupid thing in VS2005, but you can
install Web Application Project [1] that allows you to create web projects
in VS2005 that behave the same way as in VS2003.

[1] http://msdn.microsoft.com/asp.net/re...structure/wap/

Regards,

--
Martin Kulov
http://www.codeattest.com/blogs/martin

MVP, MCT, MCSD.NET Early Achiever

May 18 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.