Hi there,
ASP.NET 4.6.2. introduces a new Globalization namespace inside System.Web. This causes an issues with on-demand compilation when the existing Globalization namespace isn't prefixed with System. An example can be found here which crashes when you try to build the old index :
Admin\Content\Management\SearchEngine\Manage.aspx
The code looks as follows:
If Not DateTime.TryParseExact(indexerStatus("StartTime"), "dd-MM-yyyy HH:mm:ss", Nothing, Globalization.DateTimeStyles.None, startTime) Then
This causes .NET to crash because Globalization is now ambiguous between System and System.Web. The fix is easy; just prefix it with System:
If Not DateTime.TryParseExact(indexerStatus("StartTime"), "dd-MM-yyyy HH:mm:ss", Nothing, System.Globalization.DateTimeStyles.None, startTime) Then
There might be other cases in the code where this is an issue too.
Can this be fixed so developers can continue to work locally and rebuild the old index? 4.6.2 seems to be a mandatory part of the Win 10 Anniversary Update so more people will run into this soon.
Imar