Too bleeding edge for the moment I guess...
This whole Silverlight, EMF experience has been a roller coaster. I'm back on a down point...
Today I had finished enough on the DevTracker Silverlight project that I wanted to start publishing it on my local network. It is at the point where I wanted it for myself initially, it can create and manage projects, phases and tasks. Right now that is all I need. Even though I've come to the conclusion that not all of the technologies are perfect compared to what I had before with WPF and nHibernate, it was officially further along than any of my other projects.
So, I go into Visual Studio and publish the project. Fire up the page... error in the web.config. Microsoft is usually pretty good about this sort of thing in their products, but I could see the offending line, so I fixed it myself and re-published. Get another error, using the wrong version of .Net in IIS (4.0 vs 2.0). Go into IIS and update the application pool to use .Net 4.0... another error. I have no luck some days. Anyway, after that was dinner and I'm just getting back to the computer now. The error was telling me that my .Net framework may not be installed properly, but I doubt that since most of my development at the moment depends on it, so hopefully some web surfing in the coming days will reveal the solution.
Weird to get this sort of rough unpolished result from a Microsoft project running on Microsoft products. One of the reasons I haven't gone back to Java in the past 3 years has simply been because most times the nice automated features inside the MS products just worked as expected. For once I'm let down, the application runs fine in the dev server inside Visual Studio, since I'm deploying to another MS product I would expect it to be able to configure defaults. It even prompted me as to whether or not I wanted it to make the virtual directory into an application and then it didn't. I call this bleeding edge, but all of the applications I'm running on are RTM, not beta or even RC releases.
While I'm sure I'll figure it out... after some of the troubles with the database, WPF is looking nice again. If I can't resolve it too easily, I may convert it to an out of browser application and run it just long enough to help me re-write it in WPF using technologies I have already researched and am liking more overall. I'll lose some of the nifty short-cuts and the web hosted application portion for now, but at least I'll be back to something that works.
Today I had finished enough on the DevTracker Silverlight project that I wanted to start publishing it on my local network. It is at the point where I wanted it for myself initially, it can create and manage projects, phases and tasks. Right now that is all I need. Even though I've come to the conclusion that not all of the technologies are perfect compared to what I had before with WPF and nHibernate, it was officially further along than any of my other projects.
So, I go into Visual Studio and publish the project. Fire up the page... error in the web.config. Microsoft is usually pretty good about this sort of thing in their products, but I could see the offending line, so I fixed it myself and re-published. Get another error, using the wrong version of .Net in IIS (4.0 vs 2.0). Go into IIS and update the application pool to use .Net 4.0... another error. I have no luck some days. Anyway, after that was dinner and I'm just getting back to the computer now. The error was telling me that my .Net framework may not be installed properly, but I doubt that since most of my development at the moment depends on it, so hopefully some web surfing in the coming days will reveal the solution.
Weird to get this sort of rough unpolished result from a Microsoft project running on Microsoft products. One of the reasons I haven't gone back to Java in the past 3 years has simply been because most times the nice automated features inside the MS products just worked as expected. For once I'm let down, the application runs fine in the dev server inside Visual Studio, since I'm deploying to another MS product I would expect it to be able to configure defaults. It even prompted me as to whether or not I wanted it to make the virtual directory into an application and then it didn't. I call this bleeding edge, but all of the applications I'm running on are RTM, not beta or even RC releases.
While I'm sure I'll figure it out... after some of the troubles with the database, WPF is looking nice again. If I can't resolve it too easily, I may convert it to an out of browser application and run it just long enough to help me re-write it in WPF using technologies I have already researched and am liking more overall. I'll lose some of the nifty short-cuts and the web hosted application portion for now, but at least I'll be back to something that works.
Comments
Post a Comment