Com/Com+ confusion (all comments welcome)

[Guest]

I am in a bit of a quandry at the moment.
I have to develop 2 applications, 1 a windows app and the other thin client.
Each application will share the same business classes and the same database.

Normally I would start a new solution, add my business class project then
add my asp.net web project or windows project and continue from there.

This will result in 2 applications with bin folders each containing the
business class dll ready for deployment. The problem with this approach is,
What happens if I change my business class? Will I then not be forced to
rebuild and redploy my 2 applications ?

I have to admit that the whole subject of COM/COM+ confuses me.
I was hoping to be able to change my business classes without
rebuilding/deploying my 2 applications.

Can anyone give me a bit of advice on this subject ?

 

[Michael Nemtsev]

Hello poppy,

p> I am in a bit of a quandry at the moment.
p> I have to develop 2 applications, 1 a windows app and the other thin
p> client.
p> Each application will share the same business classes and the same
p> database.

Why do u need it? Why not to create "Common" project with common classes.
Afterwards you just add this project to your solutions.

p> Normally I would start a new solution, add my business class project
p> then add my asp.net web project or windows project and continue from
p> there.
p> This will result in 2 applications with bin folders each containing
p> the business class dll ready for deployment. The problem with this
p> approach is, What happens if I change my business class? Will I then
p> not be forced to rebuild and redploy my 2 applications ?

No, If your business classes located in different folders

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch