Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 53422 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 20396 [details]
Project System.Web-plainweb-net_4_x AND System.Web-net_4_x
The content of this file I suspect is old.
If I run exactly the same WebForms ASP.NET project on Windows 10 (VS 2015) and Mono (4.8) and MonoDevelop (126.96.36.1995) the running website shows different contents for WebResource.axd?d=<guid>
The Mono version, here, starts with author and copyright comments, followed by
The Windows version starts with
The Source I'm trying is BlogEngine.NET 188.8.131.52.
It works find except for posting comments. That's because the Mono version of WebResource.axd does not have a copy of
I've attached the Windows version.
(Suggest search of this Bugzilla using "webform" search term, as those issues could be related)
Please can you suggest a workaround.
-- Can you advise how to turn off. I've not been able to find a method to turn off the virtual WebResource.axd file. If I could, I could then add the right webform.js as a static file.
-- Can you advise whether you agree. Changing this could break a lot of current users of Mono!
-- If you are going to fix, can you advise an ETA
-- If you are not going to fix, suggest you add comment to your documentation (sorry if I've missed same). Took a day to find this difference!!
-- I guess I could Fork the whole of Mono for my own use! But that seems overkill!
BlogEngine, Fastcgi-Mono-Server, Hyperfastcgi, MonoDevelop and BlogEngine all work very well on Ubuntu 16.04
I'm really impressed.
Created attachment 20397 [details]