by Bron Skinner
18. September 2009 12:30
Alright, so after much muss and fuss I've finally found a away to get BlogEngine.NET to play nice with my existing application. I have noticed that there are still a number of errors being thrown. While they do not critically affect the application's use, I'll have to spend some time later on correcting them. I really wanted to setup another application pool to run a seperate "Forge" application from but my hosting was not terribly helpful in figuring out how to do this (not knocking them, so far they've been pretty good actually, added a couple MIME types for Silverlight content hosting for me this morning in under 20 minutes). So now the entire site is a single application running the BlogEngine.Core.dll but with redirected resources. Administrative tools still run from the root directory while actual controls, widgets, and post controls run from a blog directory. I've got the forge directory up and running as well, but I have yet to finish the backend and tie it to the near complete front end.
Essentially we create a Silverlight search widget that attaches to a locally hosted asmx (wcf is preferable but not workable in this instance for some stupid reason...maybe I'll solve this problem later). The Silverlight widget provides search options and connects to a SQL Database containing project data via the asmx. Results and then listed and hopefully look pretty, or something along those lines. On the same aspx page asSilverlight widget host control we have a gridview or templated container that populates with project data.
Now I'm not sure if I want to just invoke a function in the apsx page from the silverlight app and re-pull data or just pass data to the templated container directly. If the client already has the data, why go fetch it again?