Hi Frans,

XAML yes but much more HTML5 and CSS3 MS want to use. I just can shake my head about the reawakening of COM and unmanged/native code. Now ten years working with .NET and C# and MS want to throw it away. What's about that that .NET will be a replacement of Win32-API?

But furthermore important is what about all the companies? Like Siemens where I work at the moment. They developed all software new in the last years with .NET and WPF, WCF etc. Some big projects that where with many hundreds of developers all over the world. Shall they throw it away? Or the German Post (Deutsche Post), they developed from 2004 to 2007 all of their EPOS (Electronical Postoffice System) new with .NET (it was Clipper/xBase++ before). It was one of the first very big projects in .NET. Throw it away?

It's like the goverments e. g. change basics of their tax law.

Metro is perhaps o. k. on Tablets or Smartphones but on PCs where U have to work with a keyboard? Let's think about speech control of Windows (or former OS/2). Also Win 7 has it but almost nobody uses it on a PC but more on a Smartphone (Siri on iPhone).

Siemens started now the test cycle of Win 7 to replace Win XP. Therefore I do not believe that Win 8 will be used by the companies (very) fast, if ever.

Contemplative greetings

Reiner

rblock wrote:

Hi Frans, XAML yes but much more HTML5 and CSS3 MS want to use. I just can shake my head about the reawakening of COM and unmanged/native code. Now ten years working with .NET and C# and MS want to throw it away. What's about that that .NET will be a replacement of Win32-API?

Yeah, I fully agree. It's the old rivalry between DevDiv (the development division) and the windows division.

But furthermore important is what about all the companies? Like Siemens where I work at the moment. They developed all software new in the last years with .NET and WPF, WCF etc. Some big projects that where with many hundreds of developers all over the world. Shall they throw it away? Or the German Post (Deutsche Post), they developed from 2004 to 2007 all of their EPOS (Electronical Postoffice System) new with .NET (it was Clipper/xBase++ before). It was one of the first very big projects in .NET. Throw it away?

.NET isn't going away, it's just another toolset you can create your software with. What's important is 'relevancy': is it still relevant for the future? Perhaps not, but I don't think Metro will have any significant impact on businesses any time soon, so for at least 5 years I think desktop applications are the norm.

It's like the goverments e. g. change basics of their tax law.

Metro is perhaps o. k. on Tablets or Smartphones but on PCs where U have to work with a keyboard? Let's think about speech control of Windows (or former OS/2). Also Win 7 has it but almost nobody uses it on a PC but more on a Smartphone (Siri on iPhone).

Siemens started now the test cycle of Win 7 to replace Win XP. Therefore I do not believe that Win 8 will be used by the companies (very) fast, if ever.

I agree. We still use XP as well, mostly because it works and does what it has to do, migrating to a new OS requires re-installation and re-configuring all these tiny tools, will take ages. But we have to unfortunately... VS.NET 11 won't run on XP.

Hi Frans,

what about imaging? As I worked at Deutsche Bank PC-Systems (become later Sinius, then Siemens Business Services, then Siemens and now Atos) we developed an imaging installation and configuration. With it a PCs and Servers where installed and individually, divided by Roles or really individual, configured within 15 to 30 minutes.

Individual Data, divided by the MAC where stored in a SQL-Server DB and where managed by an ASP.NET application over the browser.

It is still, after about ten years now, in use. Lately I meet with a colleague that still works on it. It is named eBranch where is a big server farm and thin clients. If one server crashes a new one will take place and be installed from far away. The data of those machines are already in the database and still the individual software config must be copied from the defect one to the new one.

The most work is still to create the basic images. Each application is just copied and the entries are written into the registry (of course some little other work has to be made).

On a rollout in the branches the PCs already come with imaged HDs so it took just a few minutes to configure them. A whole branch, even big ones, where newly installed with hard- and software over night.

I you've more than ten or twenty PC perhaps I can ask my colleague to give U some tipps because he was the leading developer and designed this kind of installation for the bank. At facebook you find him by searching for Anthony (Thony) Brian Wall (full name and the H is important!) born in Birmingham and now already living for a long time in Germany.

O. k. I've to open a new thread because there is one thing that is a little bit annoying to me.

Writing greetings

Reiner

A bit harsh to say WPF and silverlight are dead, they'll be supported for the next two OS releases at least.

Any jobs I see out there for winforms now if for maintenance of legacy apps in general.

But U know the difference between maintenance and maintenance with further development?

And just maintenance a software is just boring to me.

I need the challenge in designing a whole new thing, the investigating for a new architecture. Just to improve a software or and some little new feature ends up often in a lazy and boring work.

Just my opinion and five cent...

rblock wrote:

But U know the difference between maintenance and maintenance with further development?

And just maintenance a software is just boring to me.

I need the challenge in designing a whole new thing, the investigating for a new architecture. Just to improve a software or and some little new feature ends up often in a lazy and boring work.

Just my opinion and five cent...

Well WPF works very well with LLBLGEN and WCF, oData/WCF/WPF also works nicely thanks to the new features in LLBLGen 3.5 (Thanks for that one frans ). Also works well with MVVM pattern which inevitably you get dragged down in Silverlight and WPF.

I've turned down plenty job offers because it's winforms, nothing wrong with the technology at all, it just bores me now and it's static.