ASP.net 2.0 makes some temporary directories that 1.1 does not. Keep ind mind that because of partial classes, code beside instead of code behind, and some new kinds of compilation options that 2.0 supports they tend to compile some things to temporary directories they did not before.
If you can't make apps in IIS XP you can run them as Flie rpojects rather than HTTP projects (that way help) or just find the ambigous files in BIN diroctory and remove one of them from the BIN directory locally so it does not see 2. App domains hide abigunies -- if IIS XP does not allow app domains removing ambiguties (i.e. DLLs in 2 places that are scoped to execute as BIN) then romeving the extra one(s) in the BIN will effectively fix that. On 12/3/05, Travis D. Falls <[EMAIL PROTECTED]> wrote: > That is kinda what I thought however, the directory it was listed was a > temp > directory created by IIS so I was confused. I think I get it now. I can't > create them as different applications, because IIS on XP doesn't allow for > that but I can check all the other directories. Thanks Charles. ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/2jUsvC/tzNLAA/TtwFAA/saFolB/TM --------------------------------------------------------------------~-> 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/
