微处理器的.NET 开发
我是一名 .NET Web 开发人员。我在这个领域有几年的经验。最近，我收到了一份在 .NET ARM 微处理器上开发 .NET 嵌入式代码的工作建议。
在微处理器上进行开发时应该预期哪些开销或问题？我知道网络开发和硬件开发是两个完全不同的领域，但芯片的开发将在 .NET / C# 中完成，正如我所说，我在这方面很有经验。
I am a .NET web developer. I have several years of experience in this field. Lately, I have received a job proposal for developing .NET embedded code on .NET ARM microprocessors.
What overhead or problems should I expect in developing on microprocessors? I know that developing for the web and for hardware are two completely different fields, yet the development over the chip will be done in .NET / C# in which as said I am experienced.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我猜您指的是 .NET Micro Framework。
您必须习惯使用有限的内存、一组有限的框架类以及松散地基于 WPF 的不同 UI 模型。
I'm guessing you're referring to the .NET Micro Framework.
You're going to have to get used to working with limited memory, a limited set of Framework classes, and a different UI model which is loosely based on WPF.
内存限制将是一个需要注意的重要问题。您最多只有几兆字节的 RAM，而且通常少于 1 MB。你会发现你以前做过的事情现在非常消耗性能。此外，微框架的有限范围有时会成为一个 PITA。但这听起来确实很有趣。我更愿意使用微型计算机而不是网络开发（我目前的工作）。
Memory constraints will be a huge thing to pay attention to. You will only have a few megabytes of RAM at most, and often less the 1 MB. You will find things you have done before are now very much performance hogs. Also the limited scope of the micro framework will be quite a PITA at times. But it sure sounds fun. I'd much rather work with micros then web development (my current job).
根据硬件的功能，您可能会在 .NET Compact Framework 上进行开发，它比 .NET Micro 更接近 .NET 桌面。
我在CF上做了一些开发，最大的缺点是被视为二等公民。您必须执行更多的 p/Invoke 操作，因为 CLR 无法涵盖许多所需的功能。你几乎总是落后一个版本（例如，VS2010 不支持 CF，而且似乎没有人知道他们什么时候会支持......）。大多数工具（从 CAB 安装程序到模拟器）都永远存在错误。您可以使用 CF 3.5，但它几乎没有桌面 3.5 所具有的任何功能，等等。
当然，内存可能是一个问题。您可能还需要跳过一些环节才能访问非易失性内存。当然，已经在那里工作的人应该知道这需要什么。
Depending on the capabilities of the hardware, you may be developing on the .NET Compact Framework, which is much closer to .NET desktop than .NET Micro.
I've done some development on CF, and the biggest drawback is being treated as a second-class citizen. You have to do a lot more p/Invoke because the CLR just doesn't cover a lot of needed functionality. You're almost always a release behind (e.g., VS2010 doesn't support CF, and no one seems to know when they will...). Most of your tools (from CAB installers to emulators) are perpetually buggy. You have CF 3.5 available but it hardly has anything the desktop 3.5 has, etc.
Of course, memory can be an issue. You may also need to jump through some hoops to access non-volatile memory. Naturally, the people already working there should know what it takes.