Update on the transition

Update on the transition | Microsoft Share Point

Update on the transition | Microsoft Share Point — Wed, 20 May 2009 20:49:40 GMT

PingBack from http://microsoft-sharepoint.simplynetdev.com/update-on-the-transition/

re: Update on the transition

Ray M. — Wed, 20 May 2009 22:35:04 GMT

The problem still is you are communicating with your customers through blogs and what not. I did quite a rant in the newsgroups on how poorly ms communicates with 'us' customers. I hoped MS would atleast get a hint of our frustrations, yet shortly after I get an automated email that my partner account has been 'frozen' (could be legit perhaps you're moving the mf stuff somewhere else, could be a mistake in te system I don't know nobody told us) emailed the only contact I still had with the team (warren) which never got back at me.

What do we need to do to get the idea though to MS that we are paying customers who chose to use the MF because it was a project MS was behind ,we payed a reasonable chunk of cash,invested quite some time into it and most of us have bosses for which 'some guy on the internet wrote on his blog that...' is not nearly good enough. I can tell you that informing your boss with "Sorry, I have no more information for you,we have to wait till that guy decides to blog again, I really hope he does soon but honestly I don't know" goes over *really* well.

You should have a list of all customers that ever licensed the porting kit, honestly write us an email that we can show our bosses to inform them whats going on and what this means in short and long term for the investmens done by your partners . Most of us have done quite an investment into the MF I think we deserve something better then just a post on 'some guys blog'.

Most embarasing question I had to answer recently was 'So the thing you convinced us to spend a ton of money on they are now planning to give away for free? Yes, thats what it looks like at the moment....'

Personally I'd like to thank you for trying to get the little information you have out to us but I'm growing more frustrated with MS as a company as this whole 'transition' thing moves along.

Like I said before we're customers, we're not *that* scary! Really email us! We promise we won't bite! Or not too hard anyway ;)

re: Update on the transition

Peter M — Thu, 21 May 2009 03:14:57 GMT

I've been looking at the micro framework with interest for a while but right now we're leaving it alone until the transition settles down - I don't want to get stuck like Ray M. with other people asking me why we started with something that had so much uncertainty.

re: Update on the transition

Steve M — Thu, 21 May 2009 07:57:52 GMT

As the president of my company, my concerns are not exactly the same as Ray's, but they are certainly in the same vane. I have a host of products/projects in the works that are all based on MF. In fact, my intention was to move 100% of my development efforts to C# and .NET/.NETMF. I have a customer right now evaluation our water AMR solution based on MF, and if they truly want to fast track a license and product development, I am screwed right now. I don't have time to change to another technology and I am not comfortable licensing what I have until I know exactly what is going on with .NETMF.

I definitely agree with Ray's comments related to being paying customers for the porting kit. I paid for mine last year. I was more than a little disappointed when I realized that it was being offered for free now, and even more concerned when I found out that the whole technology is going to be available under some type of Open Source license. I was hoping that a small group of companies could capitalize on early-adopter status and make it to market before the club grew considerably. I paid for that privilege, or so I thought.

Please understand that I don't mean to complain. I just want you guys to understand how the decisions you make, including how, what, and when to communicate with us, affect our companies. I know that we are small and not likely to generate the kinds of revenues for Microsoft that you hoped, but there are a lot of us out here and my guess is that we represent the largest part of your customer base to date.

re: Update on the transition

Jan Kučera — Fri, 22 May 2009 14:33:12 GMT

Glad to hear these news. Maybe you could also include the .NET Micro Framework SDK as a component of the Visual Studio. Not only this could bring MF to more people, but I think it would bring some confidence back.

re: Update on the transition

Roy — Mon, 25 May 2009 16:26:10 GMT

I see the MF support ARM9,so i buy a ARM9 board :2440,but i don't know how the board to run the MF,what can i do???

re: Update on the transition

Nuno — Mon, 01 Jun 2009 13:04:36 GMT

"Most embarasing question I had to answer recently was 'So the thing you convinced us to spend a ton of money on they are now planning to give away for free? Yes, thats what it looks like at the moment....'"

LOLOLOLOLOL, man you are dealing with MICROSOFT!!!, if they release the entire code base for free, it will give microframework a chance, a tiny one, but one chance.

In the embedded world, a closed system its not viable, at least for serious work....

re: Update on the transition

VG — Mon, 08 Jun 2009 19:05:01 GMT

Pretty quiet out here recently ...

Core BCL to open?

Greg — Tue, 09 Jun 2009 22:00:07 GMT

Can the core common parts of the .NET BCL be open sourced? Well known things like File I/O, socket handling, type conversion, etc are unlikely to have anything unknown to developers familiar with other platforms (e.g., CRT for C++).

re: Update on the transition

Richard — Tue, 16 Jun 2009 11:29:12 GMT

I started working with Net MF, because of it's low profile way of using just the c# code i was used to for programming desktop applications, only now target embedded devices, without having to have too much knowledge of everything that's going on beneath.

With this whole new transition thing, i'm kind-of affraid that this advantage is going to disappear, and that i have to have in-depth knowledge now of the CLR/HAL and what more, before i can get to the actual application coding...

Is my fear recognized?

Le Porting Kit du .NET MicroFramework est maintenant disponible gratuitement

Pierre's Embedded and Mobile Blog — Tue, 16 Jun 2009 14:13:23 GMT

Petit à petit, le .NET MicroFramework va devenir Open Source. C’est ce qu’annonçait Colin Miller, la