[Mono-bugs] [Bug 463941] HttpWorkerRequest.MapPath should not be used at all in profile 2.0

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=463941

User mhabersack at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463941#c3





--- Comment #3 from Marek Habersack <mhabersack at novell.com>  2009-01-24 06:43:00 MST ---
(In reply to comment #2)
> This behavior was confirmed by Microsoft to be by design in
> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=322960
It's all fine, but it doesn't give any details on how the internal
implementation of the IConfigPath et.al work - naturally, for a user of the
code the information is sufficient, but I work from the inner side and there is
virtually no documentation on the inner workings of that part of ASP.NET.

> They recommend using VirtualPathProvider but that's for ASP.NET applications
> rather than hosts.:)
Yep. Btw, we do support VirtualPathProvider now.

> IConfigMapPath is public as of .NET 2.0 SP1 (actually 3.5 was released first
> that contains 2.0 SP1) that is documented:
> 
> http://msdn.microsoft.com/en-us/library/system.web.configuration.iconfigmappath.aspx
Yes, it is public - but it doesn't make it less cryptic and more documented.
The documented part is just a tip of an iceberg. Figuring it out would take a
considerable amout of research and time, which I can't afford right now,
lamentably.

> This also means that original .NET 2.0 only has custom MapPath support for IIS
> but fortunately was addressed in SP1.
> 
> Right now I have no hosting sample code for ApplicationManager but I'll create
> some once I'll have time for that.
That will help, although I still think implementing the whole system with all
its quirks will be a huge effort as I imagine the only existing code that uses
this infrastructure is IIS7 and, obviously, we don't have access to it. It
would be really good to implement this, but I wouldn't hold my breath :)

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.