Today I spotted a weird yet intriguing contest on tor.com, saying they’ll give business cards etched into beef jerky using lasers to the first 15 people who photograph a live recreation of one of three Frank Frazetta fantasy paintings. And guess what, we did it. Hit the jump to for pictures and more info.
I recently had an issue where I converted some User Controls to code-behind model, and moved them to another directory. I then found I couldn’t reference them in code. After a post on the ASP.NET forums, I came to a solution, and devised the rules as to how you can reference a User Control in code:
If your page is inline code, you don’t have to worry about the ASP namespace. The ASP namespace is a dynamic namespace that contains the controls you referenced with the <%@ Reference %> tag in the markup file.
I hope this helps anyone having problems referencing User Controls by classname in their code. I searched for quite a while and I only got answers like “don’t use code-behind if you want to do that” or “have all your controls implement a Interface and reference them by that interface”.
Please post any comments or questions. I check my email/comments daily, so a response should be pretty quick (usually about 1 business day maximum. If I’m at a computer working, I usually respond right away). You can also contact me by email.
Earlier I posted a “solution” to a problem where I couldn’t export. I searched high and low, running through DLLs and assembly references. I thought I had it working by changing the DLL of one assembly reference the to version 10 reference (CR 2008 is version 12). I stopped the post there. Later, I realized the different assemblies were pretty integrated with each other, and you couldn’t just have different versions floating around (DUH). So I changed them all back to version 10.
Of course I still had issues with that. I forget what, but it wasn’t good. I think it wouldn’t run on the production server. That server doesn’t have Visual Studio installed, only the CR engine. The version 10 assemblies I were using were the Crystal Report packages that came with VS.NET 2008.
In order to successfully be able to use all the correct assemblies, I had to do more research. What I ended up doing was completely uninstalling Crystal Reports and reinstalling it, and configuring some Virtual Diretories. The steps and and explanation after the jump.