infolink

Tuesday, November 22, 2011

Kendo UI from Telerik coming on November 30th.

Telerik has announced a release date for the Kendo UI framework. The date they have set is November 30th.

 Kendo UI is a HTML5, jQuery-based framework which you can read more about here:

http://www.kendoui.com.

Telerik has announced a webinar scheduled for Thursday, December 1, 2011 11:00 AM - 12:00 PM EST.

You can register here for the Kendo UI webinar: https://www1.gotomeeting.com/register/335609320

Thursday, November 17, 2011

How to enable assembly binding logging using the Fusion Log Viewer

Earn easy money advertising on your blog or website: Click Here to earn money with Info Links to earn money using Click Here to earn money using adfly which simply pays you to use shortened links.

Today I had an issue with a Visual Studio 2010 ASP.Net solution. The error I was getting was:

Could not load file or assembly 'ClientDependency.Core' or one of its dependencies. Access is denied.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'ClientDependency.Core' or one of its dependencies. Access is denied.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Assembly Load Trace: The following information can be helpful to determine why the assembly 'ClientDependency.Core' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Well no matter what I did here it just wouldn't work, let alone what a confusing Registry path.
I searched around and noticed others just as confused as I was.

I eventually found the Fusion Log Viewer (x64) @ the following location "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64\FUSLOGVW.exe" Once you execute the Fusion Log Viewer, click on settings. This is set to "Log Disabled" by default.

Note: If the option buttons are disabled in the window, close the application, right click the Fusion Log Viewer, and Run As Administrator.

You can also run the log viewer by bringing up the Visual Studio Commend Prompt for your version of visual Studio, for instance:  VS2012 x86 Native Tools Command Prompt

 Make sure to right click and RUN AS ADMINISTRATOR or you will not be able to change settings to turn it on


Once you turn on the logging(Any option but disabled), you can then either use the viewer or IE to see the error on the assembly binding.

Also, you may have to restart after changing the settings for logging.

More information here:

https://msdn.microsoft.com/en-us/library/e74a18c4%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396


Once you troubleshoot your error I would highly suggest turning logging back off, as it can be unnecessary overhead.

Earn easy money advertising on your blog or website: Click Here to earn money with Info Links to earn money using Click Here to earn money using adfly which simply pays you to use shortened links.

If this helped you, please donate:
Buy Me a Beer

Telerik Updates Silverlight Site

A couple of days ago Telerik released a new version of their website for their Silverlight Controls http://www.telerik.com/products/silverlight/overview.aspx . Taking a gander through one can only be impressed. A lot of time was surely spent on all the demos.

Monday, November 14, 2011

Create Module Package not available in DotNetNuke

Recently I had an issue where I have created a module extension in Dotnetnuke 5.6.3 and no matter what I did I could not get the Create Module Package link to appear.

One of the first things I checked was the folder name, this was identical.

As a last ditch effort I simply copied and pasted the folder from Windows Explorer path to the extension wizard folder name textbox. Updated the module and there she was, the Create Module Package link was there. Not 100% sure why it didn't work before unless I simply missed a typo.

For the Create Module Package to appear in DotNetNuke, the folder name must match an existing folder in the Desktop Module folders.

Amazon1