I think private assemblies are the way to go, less hassle in many
ways. The less pages and things you have to worry about for installs,
migrations etc.
If they work as a class assembly they will work anywhere easily. As a
web app, there is much more configuration and possible issues when
trying to use the component.
>From your description it seems like you are talking more about
components rather then a big web app anyway, i might have
misunderstood though.
On 4/20/05, Mat�as Ni�o <[EMAIL PROTECTED]> wrote:
>
>
> Looking for some critique, condonement, or encourangement here...
>
> I'm planning on migrating some very lightweight web apps from Dreamweaver MX
> 2004 (hand made code) to Visual Studio 2003 but I've found that full fledged
> web apps in VS are extremely bloated and not very portable with Visual Studio
> Web Application projects.
>
> I'm thinking of basically just using Class Library Projects to work on each
> web app's object assemblies and then continuing to code the aspx UI's
> separately in Dreamweaver.
>
> Is this a good idea or should I just bite the bullet and make each app a
> full-fledged VS Web Application project and learn how to make them leaner and
> more portable?
>
> Any input would be very much appreciated.
>
> Thanks,
> Mat�as
> Manassas, VA
>
>
> Yahoo! Groups Links
>
>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
