logistical question...
-
guys... i have a website (asp.net + web service) and a desktop app (c#) that are related but not so related as to have them both in the same solution thing is i need to have a set of common classes that are used mainly for the web service ... stuff that gets shuttled bck and forth basically what is the "proper" way to share said classes between 2 projects? thnx
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
guys... i have a website (asp.net + web service) and a desktop app (c#) that are related but not so related as to have them both in the same solution thing is i need to have a set of common classes that are used mainly for the web service ... stuff that gets shuttled bck and forth basically what is the "proper" way to share said classes between 2 projects? thnx
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
I normally include the other project as an additional project in both solutions. Make sure that you add them into your application as a project reference and the up to date version gets copied in locally when you build. We also use a CI process so that changes for one application would get picked up and built in to the other application.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
I normally include the other project as an additional project in both solutions. Make sure that you add them into your application as a project reference and the up to date version gets copied in locally when you build. We also use a CI process so that changes for one application would get picked up and built in to the other application.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
thnx pete not sure i understand tho when you say: "include the other project as an additional project in both solutions" there are only 2 "solutions" ... the website and the desktop app :|
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
thnx pete not sure i understand tho when you say: "include the other project as an additional project in both solutions" there are only 2 "solutions" ... the website and the desktop app :|
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
Maybe this will help ... http://msdn.microsoft.com/en-us/library/23x5fk78.aspx[^]
-
Maybe this will help ... http://msdn.microsoft.com/en-us/library/23x5fk78.aspx[^]
thnx for the link but no... doesn't help at all
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
guys... i have a website (asp.net + web service) and a desktop app (c#) that are related but not so related as to have them both in the same solution thing is i need to have a set of common classes that are used mainly for the web service ... stuff that gets shuttled bck and forth basically what is the "proper" way to share said classes between 2 projects? thnx
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
Move the common classes into a third class library project and then reference that in both current projects.
ahhhhhhhh light in my darkness i knew that would be the method but the actual way to do it in VS eluded me thank you :)
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
I normally include the other project as an additional project in both solutions. Make sure that you add them into your application as a project reference and the up to date version gets copied in locally when you build. We also use a CI process so that changes for one application would get picked up and built in to the other application.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
ahhhhhhhh light in my darkness i knew that would be the method but the actual way to do it in VS eluded me thank you :)
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
Sorry I didn't get a chance to get back to you. I'm just back in - this was the solution that I would have pointed you towards.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Sorry I didn't get a chance to get back to you. I'm just back in - this was the solution that I would have pointed you towards.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
Some people understands in simple words. :)
Anurag Gandhi.
http://www.gandhisoft.com
Life is a computer program and every one is the programmer of his own life.
My latest article: Group GridView Data