Numerous times in recent years I’ve had to use Reflector Pro to debug third-party dlls. While this works well and allows you to step through code as if it was your own the value of doing so can be completely lost if you cannot see critical object values due them being ‘optimized away’.
Recently I was stuck with a problem of optimization that refused to be disabled by the usual means that I’d used in the past. I stumbled onto a neat trick which finally did work, but it also clarified what happens when the web application, usually Sitecore CMS, restarts.
Still much tidying up to do, but a working v0.5 alpha release now up on Codeplex
Please report any bugs or issues via Codeplex.
Fixes broken language prefix handling. Also includes multiple breaking changes since previous v0.4 release in SQL (columns, index, constraints) and codebase (interface).
This is part 2 of 2 posts on detailed Sitecore.Linkmanager configuration.
In general ASP.net, this can be caused by calling DataBind() more than once on a databound control. Also be aware that this is influenced by automatic databind being on too.
Relating this to Sitecore CMS, you should be aware that Sitecore ships with the following line in web.config:
<!– AUTOMATIC DATA BIND
Indicates if the data bind function is run automatically
<setting name=“AutomaticDataBind“ value=“false“ />
This means that you will need to either call Databind whenever you need it, or you can simply set this value to true. This AutomaticDataBind setting will also cause problems with other types of databound controls, such as templated controls. It’s generally simpler to set it to ‘true’..
After installing Sitecore v6, you get the following error when viewing the website or sitecore UI:
Sitecore Could not load file or assembly ‘System.Data.SQLite, Version=126.96.36.199, Culture=neutral, PublicKeyToken=db937bc2d44ff139’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
This is actually detailed in page 20 of the sitecore troubleshooting doc, but I missed it first time round. This is caused by the presence of System.Data.SqlLite in the bin folder when running on 64-bit OS. An alternative dll is available for 64bit OS from Sitecore.
Solution: If you’re are not using SQLite simply the delete the System.Data.SqlLite.dll from the bin folder and recycle your app to get back up and running. If you are using SQLite, download the alternative dll for 64bit OS.