[MonoDevelop] Understanding Projects and Solutions

[Tomar]

--=-BdKaLbnv294IFhFNKfn0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

You should break your applications into logical, functional units.  If
multiple applications share a common core then why not break that out
into a shared assembly?  That is the very definition of code reuse.

Copying around source code isn't such a good idea.  Handling the
finished .dll file is a much better solution.  The compiler and runtime
are oblivious to source code version but must honor assembly versions
rules.

Tom Larsen

On Thu, 2004-09-02 at 20:00, Rob Brown-Bayliss wrote:
> On Fri, 2004-09-03 at 12:53, Todd Berman wrote:
>=20
> > If your question is why can't monodevelop reference the same file in 2
> > solutions without requiring it to be a copy, thats different. But as fa=
r
> > as the referencing a single .cs file, thats just now how .net works.
>=20
> Yes, that probably is more my question.  I have been using links
> between directories, but thought that they would be a better way.
>=20
> What you  are saying then is I should make my database.cs into a dll
> rather than just part of the code?  As a total c# newbie how difficult
> is that going to be?
>=20
>=20
>=20
> --
>=20
>=20
> Rob Brown-Bayliss
>=20
>=20
>=20
> ______________________________________________________________________
> I have great faith in fools; My friends call it self-confidence.
>=20
> ______________________________________________________________________
--=20
Tomar <tomar@apricot.com>


--=-BdKaLbnv294IFhFNKfn0
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBN/mOKaYNoZecAvQRAtOvAJ9qlim07hsaJpexkNeF+aXkvZa38ACfTgDP
n8EGBnYr7wXQOXF27HxtIY8=
=+u5e
-----END PGP SIGNATURE-----

--=-BdKaLbnv294IFhFNKfn0--