It’s an exciting week here at //BUILD/, things are off to a good start. Now that the sessions are public, I wanted to let my readers know that I am giving a talk on Friday about Windows Phone Performance. Windows Phone application performance and optimization 9/16/11 from 12:30 PM to 1:30 PM Room: Marriott Orange [...]
Metro-style apps, HTML 5, XAML and Visual Studio 11 are all in your future.
Those in attendance at Microsoft's Build conference, currently going on in Anaheim, Calif., will be going home with one of 5,000 Windows 8 Tablets by Samsung.
Like many people, I watched the keynote by Steven Sinofsky at BUILD remotely – I am not one of the on-site DevExpress crew this time. Rather than rehash what the keynote revealed (after all you can watch it again if you want to), I thought I’d summarize my immediate thoughts about what was shown, especially taking the viewpoint of a software developer who’d be interested in writing apps for Windows 8. Like us and all of our customers, in essence. I’ll therefore skip over much of the details about the consumer side of Windows 8, but be aware that Windows
8 comes with a new look-n-feel called Metro that mimics the tiles and interactions of Windows Phone7. The basic interaction with Windows 8 is touch, although mouse and keyboard will still work just as well. Also the “old-style” Windows look is still there (though obviously many apps have been updated), and there were many promises that every app that runs on Windows 7 will run on Windows 8. Firstly, Sinofsky presented a bit of rah-rah stats, wrapped in a rather plain PowerPoint slidedeck. Sorry and all that, but Apple do this so much better. Anyway, it was interesting to...(Read whole news on source site)
Entity Framework Code First is a development methodology available beginning with the Entity Framework 4.1. When using Code First development you usually begin by writing C# or Visual Basic .NET classes that define your conceptual (domain) model. Your model can then be used to generate a database schema or be mapped to an existing database. You can then load data from and persist data to database using objects that are instances of the types defined in the conceptual model. By default, Code First conventions are used to automatically configure mapping between the conceptual model and database schema. Code First conventions will
work in most mapping scenarios, however, you can override these conventions with data annotations or fluent API. For more information about conventions supported by Code First, see http://msdn.microsoft.com/en-us/library/hh161541(VS.103).aspx. This post shows how to override Code First conventions using the fluent API with VB.NET. The post also demonstrates the following: Configuring database creation and initialization strategy. Retrieving and persisting data. Overriding the default Code First conventions to set the database name. Prerequisites To complete this walkthrough you must have the following installed: Visual Studio 2010 Entity Framework 4.1 Defining the Model and overriding Code First conventions In this step you will define VB.NET...(Read whole news on source site)
The commercial release of Microsoft SQL Server, codename “Denali,” will be the last release to support OLE DB. Support details for the release version of SQL Server “Denali” will be made available within 90 days of release to manufacturing. For more information on Microsoft Support Lifecycle Policies for Microsoft Business and Developer products, please see Microsoft Support Lifecycle Policy FAQ. This deprecation applies to the Microsoft SQL Server OLE DB provider only. Other OLE DB providers as well as the OLE DB standard will continue to be supported until explicitly announced. It’s important to notice that this announcement does not
affect ADO’s and ADO.NET’s roadmaps. In addition, while Managed OLEDB classes will continue to be supported, if you are using it to connect to SQL Server through the SNAC OLEDB Provider, you will be impacted. If you use SQL Server as your RDBMS, we encourage you to use SqlClient as your .NET Provider. In case you use other database technologies, we would recommend that you adopt their native .NET Providers or Managed ODBC in the development of new and future versions of your applications. You don’t need to change your existing applications using OLE DB, as they will continue to be supported, but you may...(Read whole news on source site)