I'm using NetAdvantage 10.2 with Visual Studio 2005. All worked fine for me this morning. About an hour ago, I attempted to switch one of my .aspx pages from source mode to design mode. Took forever to create each individual control. Went back to source mode and noticed the following mouseover message when I moused over the first line of source code:
"...\\ServerName\ProjectName\Index.aspx: ASP.NET runtime error: Could not load file or assembly 'Infragistics2.WebUI.UltraWebListBar.v10.2, Version=10.2.20102.1011, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417) .. "
I removed the reference and re-referenced which did not correct the problem. I rebooted my desktop which also did not correct the problem. I do not know of anything that I did since this morning that could have caused this error. Does anyone know of a possible solution?
Any help will be greatly appreciated as my development project is now unusable.
Hello megryan,
The mentioned by you exception is probably caused by code permissions of the assembly being referenced from a network share.
You can follow the approach shown in the following two articles and let me know if it works in your scenario:
http://marcoscavaleiro.blogspot.com/2006/11/failed-to-grant-minimum-permission.html
http://docs.adxstudio.com/Default.aspx?DN=225cf8b4-28eb-4742-b7d5-850823c59c07
Alex -
Thanks for the response. I took your suggestion and set the .NET Framework 2.0 Configuration LocalIntranet_Zone Permission Set setting to FullTrust. This resulted in the page controls building quickly and the mouseover message I referenced above went away. Regrettably, however, all Infragistics controls failed to build on the page and when I mouseover the first line of source code that attempts to register the UltraWebGrid assembly, a new message appears that states: " ... withEvents variable 'Header' conflicts with property 'Header' in the base class 'Page' and should be declared 'Shadows .. '. I don't recall having seen this before.
I changed the LocalIntraNet_Zone Permission Set setting back to LocalIntranet and am once again receiving the
Note: I have another project on the same server that uses Infragistics controls. I have the controls in a bin folder under this project. Both projects on the same server are giving me the error while referencing the Infragistics controls in their own bin folder. Furthermore, I have a project on a different server that uses Infragistics controls. The error is not appearing on that server.
Appreciate any further advice you can give me ...
Still have some testing to do, but it appears that I've corrected the problem. Discovered the site:
http://forums.asp.net/t/1532439.aspx/1
Created a new bin folder under my project on the server and copied the Infragistics controls from the folder C://ProgramFiles/Infragistics/NetAdvantage 2010.2/ASP.NET/CLR2/APTCA on my desktop to the new project bin folder. I also had to update the version number in my source HTML code that registers the controls on the pages that use them by setting the version number to 10.2.20102.2248.
This seemed to solve my issues.
One follow up question. Should the controls I loaded (version 2248) allow the grids to operate correctly with IE9 or do I have to load the controls that come with the IE9 service pack for 10.2? I notice they are both dated 7/7/2011 and are both version 2248. However, fixing the problem above with the controls from the APTCA folder does not seem to fix my IE9 issues unless I'm missing a step.
I located and corrected my problem. A reference to the script folder in my web.config file was pointing to an old folder. Hadn't noticed since my scripts have not changed in quite a while prior to this. My grids are working fine under IE9 after applying the NetAdvantage 10.2 service pack and changing the reference.
Thank you for your feedback. I hope that your findings will be helpful to other users too.
Build 2248 is actually the build number of the latest (and last) Service Release for version 10.2.
You should check if you updated all references and assemblies in Bin folder with the ones supplied with the Service Release. If you have some of the Client scripts modified you should change them too with the scripts supplied with the Service Release.
If the IE 9 issues are still present you can open another thread and explain them in detail there.