A compendium of Windows Azure, Service Bus, EAI & EDI,Access Control, Connect, SQL Azure Database, and other cloud-computing articles. Note:
This post is updated daily or more frequently, depending on the availability of new articles in the following sections: Windows
Azure Blob, Drive, Table, Queue, Hadoop and Media Services Windows Azure SQL Database, Federations and Reporting, Mobile Services Marketplace DataMarket, Cloud Numerics, Big Data and OData Windows Azure Service Bus, Access Control, Caching, Active Directory, and Workflow Windows Azure Virtual Machines, Virtual Networks, Web Sites, Connect, RDP and CDN Live Windows Azure Apps, APIs, Tools and Test Harnesses Visual Studio LightSwitch and Entity Framework v4+
This week I was attending the 3 day Project Ignite training. This is a technical training offered directly from Microsoft and was presented by Christophe Fiessinger and Jan Kalis at Warsaw (but I followed the training on Lync, which was really cool using the 360-video). I learned lots of new and interesting things about Project Server 2013 and Project Online. [...]
Remember the SETI
screen savers that used to be on everyone's computer? As far I as know, it was the first bona-fide use of "Cloud" computing…albeit an ad hoc cloud. I still think it was a brilliant leveraging of computing power.
My interest in clouds was re-piqued when I went to a technical seminar at the local .Net User Group. The speaker was Mike Benkovitch
and he expounded magnificently on the virtues of the Azure platform. Mike always does a good job. One killer reason he gave for cloud computing is instant
scalability. Not applicable for most applications, but it is there if needed.
I have a bunch of files stored on Microsoft's SkyDrive platform which is cloud storage. It is painfully slow. Accessing a file means going through layers and layers of software, redirections and security. Am I complaining? Hell no! It's free!
So my opinions of Cloud Computing are both skeptical and appreciative.
What intrigued me at the seminar, in addition to its other features, is that Azure can serve as a web hosting platform. I have a client with an Asp.Net web site I developed...(Read whole news on source site)
I am headed to Build later this month and am excited by both the Surface tablet and what the PC makers are going to show us in Windows 8 devices. But ahead of that show there have been a lot of reveals by the likes of HP, Dell, Lenovo and ASUS. I am perplexed by these early reveals by the PC makers. On the whole, these companies built Windows PC's in the Slate era (when Microsoft was pushing Windows Tablet Edition). Many of these new devices feel like throwbacks to the Pen Slates they built in years gone by
and that's unfortunate. Even if they don't look like Slates, they look like ultrabooks with touch screens
. Convertibles and such are interesting for the minority but not for the majority of users IMO. We need to let the PC makers know that Slates are dead...they need to be building tablets... Win8 Devices There are two types of these revealed devices: Laptops with Touch Tablets The Laptops with Touch are a good idea. These 11-17" screen laptops that add touch to them are actually a good idea. The Sony 17" one I find interesting...but I am...(Read whole news on source site)
A series of posts
providing proven guidance for developing ASP.NET MVC applications from idea to well-designed implementation.
Day 2 – Define the Domain Conceptual Model
Objective of the Day
Transform the requirements from Day 1
into an appropriate domain conceptual model reflecting objects, attributes, and associations.
User Stories or Use Cases
The domain conceptual model is a visual representation of conceptual or real-world objects in the domain of interest [Fowler, 1996
]. (The domain design model, which will be discussed in Day 3, is a visual representation of the classes and behaviors which will be implemented in the software.)
The conceptual model is
not a class diagram describing classes with methods. But in practice, the conceptual model will iteratively become the basis of the class diagram of the design model. Specifically, the conceptual model reflects the following information:
Domain conceptual objects,
Associations between conceptual objects, and
Attributes of conceptual objects.
The important distinction between conceptual model and design model is that the conceptual model should represent a clear business-oriented abstraction of the domain; i.e., the client should be able to look at the conceptual model and understand it fully without difficulty. Compare this to the design model which will include method names, data types, polymorphic associations, and...(Read whole news on source site)
I don’t know about you, but sometimes we have frequent feature branches on our projects. Sometimes we don’t go through the trouble of setting up a build configuration in TeamCity if it’s a quick feature, but sometimes we like to see the pretty green checkbox in TeamCity when our build finishes successfully…especially when more than one person is working on the feature. We also like to deploy straight to our testing environments from a feature branch occasionally for testing, so it’s important for adding a build configuration quickly and accurately in TeamCity. I thought I’d give a demonstration on
how to create one. There are two ways to make a template. From scratch and from an existing build configuration. I will not talk about the “Extract Template” option because it’s literally clicking a button and giving a name from within the “Edit Build Configuration” screen. However, there are two things you’ll need to look at in order to use the extracted template as a feature branch template. So look at steps 2 and 4 below for the details if you have an existing build to use as a template. Step 1:
Click “Create template” under “Edit...(Read whole news on source site)
Greg Young has a comment on my Rhino Events post that deserves to be read in full
. Go ahead, read it, I’ll wait. Since you didn’t, I’ll summarize. Greg points out numerous faults and issues that aren’t handled or could be handled better in the code. That is excellent, from my point of view, if only because it gives me more stuff to think about for the next time. But the most important thing to note here is that Greg is absolutely correct about something: I have always said an event store is a fun project because
you can go anywhere from an afternoon to years on an implementation. Rhino Events is a fun project, and I’ve learned some stuff there that I’ll likely use again letter on. But above everything else, this is not production worthy code .It is just some fun code that I liked. You may take and do whatever you like with it, but mostly I was concerned with finding the right ways to actually get things done, and not considering all of the issues that might arise in a real production environment....(Read whole news on source site)