Last post Jul 24, 2006 08:16 PM by phuff
Jul 22, 2006 02:12 PM|ligaz|LINK
It is great that you guys have spare time to work on such cool projects (Nikhil's Script# also rocks da house). The name is also very awsome - weBLINQ - cool.
I have been using LINQ since its first release in a web app on my own. And there were some problems with the web's disconnected model, but know with the May CTP the things are better.
So here is my list of features for Blinq:
The best will be if you put this open source. You've open the providers implementations. Why not this also? It will be blast if it is community driven as Atlas Control Toolkit.
P.S. Polita why don't you start a blog? :)
Jul 24, 2006 08:16 PM|phuff|LINK
1. The templating/extending the page generation feature is something several people have asked for. We've taken it as a possible feature for the Blinq features in the next version of Visual Studio and are talking about the best design for the feature.
2. I definitely agree that UpdatePanels would be a great addition to Blinq. I considered it but ultimately nixed the idea because there are several releases of Atlas out there and I didn't want to have to require a certain version. The Atlas releases have
generally contained lots of breaking changes, so I would have had to choose a target version, and that may put some customers in a tough position. My thought around UpdatePanels for Blinq is that you can quickly put all data controls on all pages inside an
UpdatePanel by adding the UpdatePanel to the MasterPage and put the ContentPlaceHolder inside the UpdatePanel. This is a fairly simple change, so hopefully it will work for you.
3. The DLinq designer came online too late for the Blinq preview. I agree that it would be far nicer to have a UI to choose your tables. The DLinq designer will be part of the Blinq solution we build for Visual Studio.
4. Splitting up the generated static methods into separate files based on class is an interesting idea. I tried hard to not generate a lot of duplicate code- can you be a little more specific about what code you feel is redundant?
I don't have a blog because I just don't have enough time to do a blog justice. Every now and again I consider it, but I'm not sure I have the discipline to keep it from becoming one of those cobwebby abandoned "I had the best intentions" blogs. [:)]
Thanks for your feedback- we're listening and trying to build Visual Studio's features with as many of the most common requests as we can.