the only thing I can think of that would keep .NET from being embraced by consumer windows is if there are security flaws in .NET apps. And I don't know enough to say that or not. But Windows 7 and earlier PCs are way too much of a hassle for users in terms of getting viruses.
... but Windows, as an organization, is infinitely more open and transparent than Apple.
Microsoft wants to be more like Apple. Apple makes a lot of money.
Windows 8 looks to be about splitting Windows in two parts. Windows used by businesses. Which need programming. And Windows used by consumers. Which needs apps.
Build is likely to be about how to write apps that will be sold thru and deployed by Microsoft onto the consumer windows desktop. A great opportunity for programmers to make some money. But I would not expect a programming paradigm breakthru. If anything, there will be more than a few restrictions regarding what your app can do and how much access it has to the resources of the PC.
For the user to get to the browser they first see the desktop. On the desktop is a tiny icon that says "browser". The remainder of the space is taken by apps the platform provider has placed there. To buy a book or video game and download it to your tablet you can open the browser and navigate to amazon. Or enter directly into the desktop app that takes up a 1/4 of the screen space and is customized for the particular user's use.
Consider that you have to register with MSFT and then pay a $99 annual fee to deploy an app you have written to your windows phone. Consider also that you cannot run the .NET micro framework on a cell phone.
Something else. Apple is hugely suceessful and profitable despite the fact that the programming languages and frameworks used to code Apple apps are inferior to .NET/C#
The conclusion is that apps written the old fashioned way, by individuals and organizations which are going to use those apps, don't matter. They don't matter that is to the profitability of the company that produces the platform. They also don't matter much to the popularity of the platform.
Windows 8, I am guessing, is all about Microsoft's attempt to bring an IPhone like ecosystem/profit center to the PC desktop. Think of the potential for profit to the provider of the desktop if the user runs a desktop app to make a plane or hotel reservation. Or it a desktop app is used to download and view a movie to their home theater system.
In order for the platform provider to funnel a user's usage of the PC thru its desktop apps, that desktop has to be locked down. At a minimum, a portion of the desktop has to be reserved for apps the platform provider approves of.
Arguably, there is a conflict between individuals who write and distribute apps the traditional way,.direct from developer to consumer, and the new Apple / desktop lockdown way. The new way enables the owner of the OS to profit from the daily use of the PC.
just to complete the circle. I reboot the PC and excel no longer crashes. My PC hardware is not that bad. IE9 crashes maybe once a month.
Visual Studio Tools For Office
I will check on VSTO again. I am looking to put a combobox in a cell that is populated with season codes from a database. Select a season code and the combobox and the cell to the right is populated with styles for the season. Which cascades to a combobox with the colors of the style.
Was going to use the .Validation property of a cell to do this, but the validation list is limited to some limitation that likely dates back to 1992.
Does VSTO replace VBA? Can I double click a cell in the spreadsheet and run .NET code that pops up a WPF form and then populates a row in the spreadsheet from the .NET code? I can attach the VSTO project to an excel spreadsheet just like VBA code? The VSTO code will run on Excel 2007?
I have isolated what is crashing excel 2010 on me. When the button click handler assigns a value to the active cell, excel crashes. Run the code with that single assignment statement commented out, and it runs ok.
-- worksheet double click handler news up a VBA form:
Private Sub Worksheet_BeforeDoubleClick(ByVal Target As Range, Cancel As Boolean)
Dim fm2 As frmDummy
Set fm2 = New frmDummy
Set fm2 = Nothing
-- ok button click handler assigns a value to the active cell. excel 2010 crashes.
Private Sub butOk_Click()
Set r1 = ActiveCell.Offset(0, 0)
r1.Value = "abc" ' <== comment this out. excel does not crash.
Set r1 = Nothing
I am hoping to write some VBA functions that connect an excel spreadsheet user to an ODBC data source. Excel 2010 is crashing left and right on me and hours into the process I can't find the cause. Take away code bit by bit until it stops crashing. Then you put the code back and it still does not crash. Then, put the app back that I had renamed and run it. And it crashes.
Anyway, I am very happy that Access has been replaced by lightswitch. Is there a .NET version of Excel anywhere on the horizon?