We switched to Visual Studio 2010 Beta2 because we need to use Entity Framework 4.0 (edmx). However, the ultrawebgrid does not seem to work with this version. We are getting
Stack Trace: at System.Boolean.Parse(String value) at System.Web.Configuration.HttpCapabilitiesBase.CapsParseBool(String capsKey) at System.Web.Configuration.HttpCapabilitiesBase.get_JavaScript() at Infragistics.WebUI.WebControls.ClientMachine.FillValues(Control control) at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.get_Client() at Infragistics.WebUI.UltraWebGrid.UltraGridLayout.Infragistics.WebUI.UltraWebGrid.IParticipateInAppStyling.InitializeStyles() at Infragistics.WebUI.UltraWebGrid.GridWebAgent.InitializeStyles() at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.Infragistics.WebUI.Shared.IProvideAppStyling.InitializeStyles() at Infragistics.WebUI.Shared.CssBuilder.AppendStyles(Boolean clearStyles) at Infragistics.WebUI.Shared.CssBuilder.AppendStyles() at Infragistics.WebUI.Shared.CssBuilder.OnPreRender(Control control, Boolean preRenderComplete) at Infragistics.WebUI.Shared.CssBuilder.OnPreRenderComplete(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Page.OnPreRenderComplete(EventArgs e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
We need to make this work badly in VS2010 .net 4.0, any ideas?
We managed to solve this issue (or so we hope - so far it's working). The error is that IG asks for a Browser capability of "javascript", which is obsolete. ASP.NET 4 Default.browser file seems to be missing this property, and therefor it returns 'null' when asked for. The bool.Parse method fails to parse "null" and that's the cause of the exception (see your stacktrace).
What we did was simple: add a browser file to App_Browsers folder (e.g. DefaultEx.browser), and add the missing "javascript" property yourself:
<browsers> <browser refID="Default"> <capabilities> <capability name="javascript" value="false" /> </capabilities> </browser></browsers>
Hello,
We have made some fixes since beta 2 was released. Can you provide more information on this issue, possibly a sample so that we can try to figure out what is causing it and fix it. We have been working with Microsoft and they've also made changes since beta 2. In the latest LCTP a lot of issues have been fixed. I am not sure if you have access to their latest LCTP, if you do, can you try it out and see if it fixes it?
Let me know if you continue to see this issue.
-Taz.