MVC 2 Breaks my Charts?

I wonder if anyone has had issues with running MSCharts with MVC 2?  I have tried a couple of different issues, but still have not got them to render correctly.  In the end I always end up with broken image links.  Has anyone seen this?

I have no errors displaying in my MVC 2 Application build or anything, nothing specific that leads me to any explanation.  If anyone has any ideas, please leave a comment or shoot me an e-mail; adronhall at gmail dot com.  I would greatly appreciate any insight you MSChart Elite may have.  : )

ADDITIONAL NOTE:  The links look like this:

http://localhost:1799/Scorecard/ChartImg.axd?i=chart_6d740211d16b41bd9cc2662b602c4045_0.png&g=8840cdffa191495caafa73150dc0de7d
Which I assume is what they should look like, since the ChartImg.axd is supposed to be handling the requests for the chart images.  Maybe the handler is broken/messed up?

Egads, Come on Hosting Provider!

I was looking at my analytics over the last week or so and am really annoyed.  I had a solid multiple hours of downtime over the weekend.  Of all times, while I am at ALT.NET Seattle #altnetseattle Conference for my hosting provider to go down.  I would have liked to make blog entries, but instead they got all crammed up.

Anyway, I just wanted to post my massive hit I took because of this.  I do hope that webhost4life improves this and it doesn’t happen again.  My uptime has usually been remarkably good, but this was horrendous, easily breaking my 99% plus uptime promise.

Look at that dip!??!  Come on webhost4life, how about that not happening again!  73% down against regular trends, which if I had that 99% uptime I would have at least gotten the majority of the hits for that day.  Which would have been a decent percentage increase over the previous trended period since I was at a conference!

Harumph.  : (

NxBRE Integration and Visual Studio Team Server Strangeness

So after a far longer process than I originally had planned on (fortunately I had saved a ton of time by using a prebuilt solution such as NxBRE) I acheived a building integration of the NxBRE Project into the primary Visual Studio Solution.  No particular fault of NxBREs it is just that some of the references and other items got fubared when moved across.  That leads me to…

…Visual Studio Team Server’s Source Control would NOT let me just add the project.  I’m not sure what the deal was with that, but it was determined.  What I had to do in the end was literally do a manual creation of a project and name it the same, then add all the files as one would existing code files.  After working out the bugs everything seems hunky dory.  Gracious though it was a bit of excessive work that I didn’t really need to focus on at this time.

Now that this is done I intend to in the next few days create some examples and stick them up on the site in relation to utilizing NxBRE.