As a part of our annual outings had gone to Goa and my native place near the coastal city of Karwar...Truly God's own country I would say...Refreshing air, rejuvenating environment and loads of simplicity...You end up thinking ..whether how we(urban) people end up with all these complications in front of the simple life people lead in villages..Fully Geo friendly and optimized for the basic needs of man, resources are used only to the extent absolutely needed and rest of the nature thrives ..
Now back to the city and the madness around Mumbai..Start work soon..
Monday, December 27, 2010
Saturday, December 11, 2010
Telerik RADTabStrip's weird behavior
Recently I have come across a very strange behavior in the Telerik RADTabStrip. A perfectly fine working code base suddenly started having a "Freeze" behavior in 2 out of the 4 environments we have. What I mean is, the TabStrip just locks up on the first load. Once there is a postback on the page, it starts working perfectly fine as if nothing had happened.
We tried resorting to all the typical tricks that Telerik has recommended and some of the settings that the Forum visitors asked us to use but to no avail. Some ideas were around validation, others around naming the user control and some around checking the JS/CSS issues...NOTHING! as yet..
Wonder if anyone can help me..
Meanwhile India whitewashed the NZ series and now head to SA. Lets see what kinda duel we have in store there...Hmmm!
We tried resorting to all the typical tricks that Telerik has recommended and some of the settings that the Forum visitors asked us to use but to no avail. Some ideas were around validation, others around naming the user control and some around checking the JS/CSS issues...NOTHING! as yet..
Wonder if anyone can help me..
Meanwhile India whitewashed the NZ series and now head to SA. Lets see what kinda duel we have in store there...Hmmm!
Sunday, December 05, 2010
Latest Status on Oslo...Oslo, Quadrant and the Repository is dead, long live “M”?
In October 2007, Microsoft introduced “Oslo” as the codename for a set of technical investments to apply model-driven principles to building applications and services. Since that announcement, many of those investments have shipped in products such as the .NET Framework, Windows Server AppFabric and Windows Azure AppFabric. This note is an update on the three “Oslo” investments that have yet to ship: the “Oslo” repository, “Quadrant”, and “M.”
Microsoft created the “Oslo” repository to make the model of a system or application easily accessible without relying on application-specific machinery to consume or query those models. The “Oslo” repository achieved this by storing the models for applications and systems in a shared SQL Server relational database.
Over the past year, customer feedback prefering a more loosely-coupled approach; specifically, an approach based on a common protocol and data model rather than a common store has forced MSFT to shut down Quadrant and the Repository. The momentum behind the Open Data Protocol (OData) and its underlying data model, Entity Data Model (EDM), shows that customers are acting on this preference.
With OData, Microsoft has enabled access to information across a growing number of technologies, data sources, and tools, including .NET Framework, Visual Studio, Microsoft Excel Power Pivot, SQL Server Reporting Services, SharePoint 2010, Windows Azure storage, and Codename “Dallas.”
With EDM, they have created a common abstract model for data that can be represented in multiple forms (XML-based EDMX/CSDL, C# or Visual Basic classes, visual designers, OData metadata) to simplify the creation and sharing of models.
Microsoft created a language codenamed “M” for defining schema, constraints, queries, and transformations. While they used “M” to build the “Oslo” repository and “Quadrant,” there has been significant interest both inside and outside of Microsoft in using “M” for other applications. Microsoft is continuing their investment in this technology and will share our plans for productization once they are concrete.
Microsoft created the “Oslo” repository to make the model of a system or application easily accessible without relying on application-specific machinery to consume or query those models. The “Oslo” repository achieved this by storing the models for applications and systems in a shared SQL Server relational database.
Over the past year, customer feedback prefering a more loosely-coupled approach; specifically, an approach based on a common protocol and data model rather than a common store has forced MSFT to shut down Quadrant and the Repository. The momentum behind the Open Data Protocol (OData) and its underlying data model, Entity Data Model (EDM), shows that customers are acting on this preference.
With OData, Microsoft has enabled access to information across a growing number of technologies, data sources, and tools, including .NET Framework, Visual Studio, Microsoft Excel Power Pivot, SQL Server Reporting Services, SharePoint 2010, Windows Azure storage, and Codename “Dallas.”
With EDM, they have created a common abstract model for data that can be represented in multiple forms (XML-based EDMX/CSDL, C# or Visual Basic classes, visual designers, OData metadata) to simplify the creation and sharing of models.
Microsoft created a language codenamed “M” for defining schema, constraints, queries, and transformations. While they used “M” to build the “Oslo” repository and “Quadrant,” there has been significant interest both inside and outside of Microsoft in using “M” for other applications. Microsoft is continuing their investment in this technology and will share our plans for productization once they are concrete.
Saturday, December 04, 2010
MS Tech breakup
As I continue to look into areas that will be growth islands in the MS domain, following topic come to mind:
- MS Cloud services (Azure)
- MS Web Platform
- MS SOA based technologies
- SQL BI
Subscribe to:
Posts (Atom)