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

ASP.NET 2005 Solution Problem

P: n/a
I'm developing a web service that will eventually be sent to other like
organizations to communicate for a particular application. After a few
weeks, I decided it would be better to split of the web service and custome
code from the required code. In doing so, I created a class project.

This left me with a new solution of a web site and a class. I had
previously created the class seperately and added it to sourcesafe. I then
added the class to the web service project, which is where the solution was
created.

Two problems with this and sourcesafe. 1) If I add the solution and web
service to sourcesafe, the next time I open the solution from sourcesafe, the
web service no longer functions properly. It seems you can't add any
references to it and some that were there can no longer be read. 2) If I add
just the website, that works, but the next time you want to open the solution
and change part of the class and redeploy, the class does not exist, needs to
be readded, updated, etc... which is not correct.

Can anyone decipher this problem? What is the correct method to build this
type of solution and how to add it to sourcesafe? Are there any documents
out there discussing best practices in storing, creating, etc... in
sourcesafe?
Feb 2 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
two options.

1. make a seperate project file to compile the class and add the project to
the web solution.
2. in vss, share the class file to the webservice dir.

-- bruce (sqlwork.com)

"mkd1919" <mk*****@discussions.microsoft.com> wrote in message
news:10**********************************@microsof t.com...
I'm developing a web service that will eventually be sent to other like
organizations to communicate for a particular application. After a few
weeks, I decided it would be better to split of the web service and
custome
code from the required code. In doing so, I created a class project.

This left me with a new solution of a web site and a class. I had
previously created the class seperately and added it to sourcesafe. I
then
added the class to the web service project, which is where the solution
was
created.

Two problems with this and sourcesafe. 1) If I add the solution and web
service to sourcesafe, the next time I open the solution from sourcesafe,
the
web service no longer functions properly. It seems you can't add any
references to it and some that were there can no longer be read. 2) If I
add
just the website, that works, but the next time you want to open the
solution
and change part of the class and redeploy, the class does not exist, needs
to
be readded, updated, etc... which is not correct.

Can anyone decipher this problem? What is the correct method to build
this
type of solution and how to add it to sourcesafe? Are there any documents
out there discussing best practices in storing, creating, etc... in
sourcesafe?

Feb 2 '06 #2

P: n/a
This is the warning message I get when I add the solution to vss, which
includes the new website and the previously created class.

The project that you are attempting to add to source control may cause other
source control users to have difficulty opening this solution or getting
newer versions of it. To avoid this problem, add the project from a location
below the binding root of the other source controlled projects in the
solution.

Once I do it and attempt to open the solution from vss, the class files
contained under app_code on the website come up with errors. The errors are:
Type 'Exception' is not defined
Type 'ConfigurationManager' is not defined
Type 'Math' is not defined
Type 'IO' is not defined
Type 'Int32' is not defined
Type 'DateTime' is not defined

This all worked before adding and pulling the solution from vss???
"Bruce Barker" wrote:
two options.

1. make a seperate project file to compile the class and add the project to
the web solution.
2. in vss, share the class file to the webservice dir.

-- bruce (sqlwork.com)

"mkd1919" <mk*****@discussions.microsoft.com> wrote in message
news:10**********************************@microsof t.com...
I'm developing a web service that will eventually be sent to other like
organizations to communicate for a particular application. After a few
weeks, I decided it would be better to split of the web service and
custome
code from the required code. In doing so, I created a class project.

This left me with a new solution of a web site and a class. I had
previously created the class seperately and added it to sourcesafe. I
then
added the class to the web service project, which is where the solution
was
created.

Two problems with this and sourcesafe. 1) If I add the solution and web
service to sourcesafe, the next time I open the solution from sourcesafe,
the
web service no longer functions properly. It seems you can't add any
references to it and some that were there can no longer be read. 2) If I
add
just the website, that works, but the next time you want to open the
solution
and change part of the class and redeploy, the class does not exist, needs
to
be readded, updated, etc... which is not correct.

Can anyone decipher this problem? What is the correct method to build
this
type of solution and how to add it to sourcesafe? Are there any documents
out there discussing best practices in storing, creating, etc... in
sourcesafe?


Feb 3 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.