rwandering.net
The blogged wandering of Robert W. Anderson
Archive for .NET
August 21, 2010 at 5:31 pm · Filed under .NET, Grid Computing, Web 2.0
PDC10 is coming up in late October. I signed up for it knowing it was Azure-centric, but I am glad to see that there is also a .NET track. I hope this will include non-Azure server side technologies (e.g., EF, AppFabric for Windows Server and the like). Of course these other pieces all have their place (or counterparts) in Azure, but I don’t think I’ll be using Azure directly over the next year.
PDC’s are quite valuable to attend (access to Microsoft product teams, exposure to their roadmap, opportunity for light-bulb” moments, etc). That said, I may decide not to go after the session list is released – a simple balancing of priorities.
Anyway, I’ll likely keep my registration – I would actually love it if Microsoft could change my plans about Azure this October.
Are you going? Or not? If so, please share your reasons.
Tags: .NET, Microsoft, PDC, PDC10
July 6, 2010 at 10:41 pm · Filed under .NET, Grid Computing
We recently released the Digipede Network 2.4. Among other things, this release provides support for hosting .NET 4 applications, some new features to improve management and control, and enhanced server-side performance. The entire list and downloads are available on the community site. You can read more about it on the Interwebs:
Those paying close attention might ask "what happened to 2.3?" The answer is Digipede trivia.
- Part of a failed experimental branch? No.
- Is 2.4 actually numbered 2.3.1 under the covers? No. (A minor dig at Windows 6 R2).
The actual reason dates back to the days when .NET 2 was released. Back then, we were ready to release Digipede Network 1.1 with .NET 2 support. To avoid naming confusion with .NET 1.1, we decided to skip the “.1” and went straight to “.2”. Was it in fact less confusing? Probably not materialy.
So, why no 2.3? It is an ever so slight (and obscure) homage to those early days: for .NET 4 we decided to release something that ends in “.4”.
Like I said: trivia.
Tags: .NET4.0, Digipede, grid
April 26, 2010 at 7:35 pm · Filed under .NET
CA2204: Literals should be spelled correctly (docs here).
I agree, but it doesn’t work.
At least not with compound words. If you are authoring a reusable class library, you are bound to have compound words in literal strings. Do yourself a favor and turn off the warning.
I had to search around to get this acknowledged, and finally found it on Microsoft Connect here.
Tags: .NET, Code_Analysis, FxCop, VS2010
March 19, 2010 at 9:22 pm · Filed under .NET
I was looking at the solution for a Windows Server AppFabric class (from this Microsoft download) and found a funny namespace used for the WCF contracts:
http://www.demo.com/fourthcoffee/entities/1
First thought, isn’t the demo.com domain owned by the DEMO conference?
Uh, yup.
Not a good idea to use a “random” URI for namespaces.
The content for the class looks pretty good, but I’m surprised that neither Ron Jacobs nor Zoiner Tejada caught the problem namespace.
Tags: AppFabric, DEMO, tempuri
March 18, 2010 at 12:09 pm · Filed under .NET
I’ve been looking a bit at .NET 4 Workflow Services as a part of AppFabric. I’m surprised to find no way to build these services from existing message contracts. I can understand imposing limitations on doing so – even that there might be no reasonable tool support – but this is a real stumbling block.
Certainly contract-first is not the only way to build services, but it is if you are implementing a published standard. Maybe there is some way to tinker around with the output of the tools sets to make a Workflow Service compatible with some existing WSDL, but would it be worth it?
One answer might be to put a pure WCF facade over the Workflow Services. Kind of a headache, but maybe workable.
This makes me think that .NET 4 Workflow Services are really targeted to be internal to the enterprise or at least where contract definition is flexible and controlled by one entity.
This follows a standard Microsoft pattern: help the enterprise dev in V1 and then expand from there. This strategy makes sense, I just want it all in VS 2010, not in V.next.
Tags: .NET4.0, AppFabric, VS2010, WCF, WF
February 3, 2010 at 2:55 pm · Filed under .NET, Miscellaneous
All this talk about Flash on the iPhone/iPad . . . Why does Apple freeze out Flash? Here’s why:
- 1% battery life. If Apple is willing to cripple the phone with no background applications to save battery, then I can believe that disallowing Flash supports this same cause.
- 1% of this is that Flash is “lame” or proprietary or any of that nonsense.
- 98% of this about the App store. Apps delivered through the browser can’t be monetized (and to a lesser extent controlled) through the App store. If Flash was enabled on the iPhone anybody could write apps for the iPhone without Apple’s permission.
That’s it.
The iPhone is as open as is useful to Apple. I’ll bet that if they could get away with shutting off Javascript on the iPhone they would do that too. Of course, that would also cause an enormous uproar, so they won’t. Javascript in the browser is the leak in the App store. Their only defense is to make their browser lame (or be slow to adopt new standards).
One thing that backs up my point about the App store is that neither the Flash nor Silverlight runtime is actually banned from the iPhone. You just have to build it into an iPhone application for the App store and you are in business. Miguel de Icaza and his excellent team proved that last year (with Mono anyway) as has Adobe with Flash.
What do I think about this? I find it irksome to say the least, but I didn’t buy the iPhone thinking it was anything but a closed platform, controlled by someone who thinks they know best. I’m OK with that for now – the phone works pretty well. Eventually something will work just as well without the restrictions.
And then I’ll jump ship.
November 18, 2009 at 4:05 pm · Filed under .NET, Attention, Miscellaneous, Web 2.0
Lots of great new stuff in today’s beta. A few things that stand out:
- Hosting HTML
- Context menus
- WCF and REST enhancements
- Support for RIA Services
- Drag & Drop
- Running out of sandbox for trusted apps
- Sharing components between .NET 4 and SL 4
Lot of other things too. I’m excited to start using this. Also a shout out to Tim Heuer – he has helped me on a few things before and I got a chance to meet him today.
Those of you following NewsGang will know why I am very excited about these Silverlight developments.
Tags: .NET4.0, NewsGang, PDC09, PDC2009, Silverlight
November 18, 2009 at 11:27 am · Filed under .NET, Miscellaneous
Sinofsky talked about the new features of Windows 7 and some of the new hardware. I didn’t think it belonged in the keynote, because there weren’t any announcements.
He did announce they are giving away laptops to all attendees, though, so I suppose it was worth it.
Tags: PDC09, PDC2009, Windows7
November 17, 2009 at 6:41 pm · Filed under .NET, Grid Computing
Lots of improvements to EF for 4.0:
- Model-first development.
- Lazy loading through relationships (i.e., no longer have to call Load)
- POCO (i.e., define your own data classes against a model).
- POCO only (i.e., define the model fully in code).
- Code Generation options using the new T4 facility of VS 2010.
- Testability improvements through IObjectSet
- Can override SaveChanges
- Better disconnected workflow (both by writing a little code and a no-code option that uses a different code generator).
- Much better SQL (more compact, more efficient)
- Execute arbitrary SQL
- Easier Stored Procedures
- Functions (a little strange how this was implemented, but now they are available).
- Foreign Keys in the entities (no more manual interpretation of the Reference!)
- Better Binding for forms apps and WPF
Pandelis, what do you think?
Tags: .NET4.0, Entity Framework, PDC09, PDC2009
November 17, 2009 at 6:31 pm · Filed under .NET, Grid Computing, Web 2.0
At last year’s PDC, I posted
It is the openness of this platform, the ability of developers to mix and match the different components, and to do it between the cloud and in-premises solutions that makes this such a winner.
This last point is an important one. Microsoft is in a unique position to help enterprise IT bridge to the cloud. While I don’t think Amazon and Google will cede that market to Microsoft, their current offerings aren’t a natural fit.
The offering was rich then, but since then Microsoft has continued to push these offerings forward dramatically.
At the time, my biggest concerns were the one-size-fits-all approach to their provisioning model and their lack of full trust (two things that could make it harder to deploy the Digipede Network onto Azure). Today those issues have been taken off the table and help support many more use cases, opening up Azure even more to non-Microsoft technologies and fortifying the extremely important IT bridge.
So what are the improvements in openness?
Allowing full trust opens up the door to, well anything. Unmanaged code, PHP, MySQL, Java, TomCat, etc. can all run on Azure. Matt Mullenweg of Automattic demonstrated a WordPress instance running that way. Kind of anti-climactic, because it would have been a big deal if wordpress.com was moving to Azure. Simply running a WordPress instance isn’t really that interesting.
Custom VM images are also coming to Azure which will make it much easier to put whatever you want on a VM and deploy it efficiently.
For IT?
Too many items here to enumerate. SQL Azure integrating into SSMS; Azure integrating into MOM; SQL synchronizing with cloud instances; (this list really does go on and on . . .).
Another important part of this IT bridge? Not Microsoft’s new App Server, AppFabric. Though I am excited about this – it is something that has been missing from the Microsoft stack – the key point here is that it runs on premises and in Azure.
Conclusion?
These new features in Azure push Microsoft out even further than the other cloud vendors. No one else has the depth and breadth in tool support and service offerings. No one else is innovating so quickly on so many parallel fronts.
Will Amazon and Google cede the space? Of course not, but I think they’ll need to reposition their cloud brands.
Tags: AppFabric, Azure, PDC09, PDC2008, PDC2009
Next entries »