My day job is using the compact framework but as a home/side project I'm starting to learn Android development.
Having seen Androids traceview (a visual profiling tool) does anyone know if there's anything similar for .net and the compact framework (version 2)?
Look at EQATEC's call profiler.
The Power Toys for .Net 3.5 Compact Edition has a profiler called NETCF CLR Profiler. That is the closest thing I know about -- but it doesn't give you quite as much as you get with Android's TraceView.
Related
Can anybody recommend gauge components for Compact Framework applications?
The only gauge toolkit that I've found so far is Perpetuum's Instrumentation Widgets for PDA. Perpetuum's gauges aren't visually appealing to me and also seem to be supported only up to .NET CF 2.0. Are there any alternatives?
At least one alternative is in smart device framework. http://www.opennetcf.com/library/sdf/
RoundGauge in OpenNETCF.Windows.Forms It isn't very fancy though so it may not be what you're looking for.
Looks like I found a good commercial variant, but I'm looking exactly for Free one. Does someone know some?
How about the OpenNETCF ORM? It's free, lightweight, and was built specifically for the Compact Framework, then ported to other platforms (as opposed to someone shoehorning a desktop ORM into the CF).
I am currently looking for a free .net ORM for use on Windows CE. So far I have found these commerical options:
DevXpress XPO
LLBLGenPro
EntitySpaces
NHibernate sadly is not an option because it uses features that are not available in the Compact Framework (e.g. reflection related functionality).
If using a SQL database as your underlying data store is not absolutely necessary then Karvonite is worth consideration. It is a free (Ms-PL) object persistence framework compatable with the .net Compact Framework. Do you need to use SQL Server Compact or are you really just wanting an easy way to persist your domain?
I will update you if I find more options.
I built DapperLite to work on .NET Compact Framework and full .NET. It's basically a Dapper clone, so it's a single file under 200 lines you can drop into your project.
I had tried OpenNETCF.ORM but found it too opinionated. I love using Dapper in my desktop apps but unfortunately it doesn't work with .NET Compact Framework.
I also built a Micro-ORM layer over the top of DapperLite to make it a bit easier to use, which is essentially a clone of Dapper.Rainbow
Is there any code conversion tool for converting Delphi to Visual Basic? Please advice.
Thank you very much.
Not that I'm ware of. There are tools to convert Delphi to C# or Visual Basic to Delphi. But not the other way around. It's probably because Delphi has a lot more features then Visual Basic to make it a difficult transition.
You can do it by hand. But it'll take a while.
If you consider moving to VB.NET (and .NET platform in general butnot VB6), these questions might give you some ideas/options:
What tools exist to convert a Delphi 7 application to C# and the .Net framework?
Is there an easy way, to Port a Win32 App in Delphi 2009 to .NET ?
Migrating a Delphi 7 application to .NET
Delphi to .NET + C#
Delphi’s interoperability with .NET
You can try migrating the application from Delphi (Win32) to Delphi.NET or Delphi Prism
Once this step is complete you can consider migrating to VB.NET or C#
But it really depends on the technologies used by your original application (e.g. BDE, 3rd party components), level of interaction with WinApi and so on.
Delux Software has one.
I'm already new in C++CLI , although I have been working on VB and C++ for a long time , but I need to start a projects on CLI using it's visual screens and easy codes (just in windows) , But I can't find any good Resource or book to start windows programming (I mean codes that you can give it to buttons or texts without using c++ classes) ,
Can I find any of them ?
thank you
I can suggest you 3 books ( I used them ):
Foundations of C++/CLI The Visual C++ Language for.NET 3.5
Pro Visual C++/CLI and the .NET 3.5 Platform
C++/CLI in Action
They are in order of difficulty.
The first and the 2nd are introductory and advance respectively.
The 3rd is great for advanced topics, like interop, mixed-mode coding etc..
Not sure what you have done in your work with C++ without classes, it is C with classes :). If you want to write Windows Program in C, Programming Windows, 5th Edition written by Charles Petzold could be a good start. Then you can decide which managed GUI to learn. Winform is mature with no future planned beyond .Net 4.0, while WPF is growing and is the main focus of Microsoft.
I heard from a friend that Microsoft rewrote all the Windows Workflow Foundation (WF) again and changed everything was in .Net 3.5.
Is that true?
And what about what we learned about WF in 3.0 and 3.5?
According to this article:
http://visualstudiomagazine.com/articles/2009/01/01/windows-workflow-changes-direction.aspx
Windows Workflow Foundation 4.0 is a "bottom-up rewrite with entirely new thinking...WF 3.0/3.5 will remain part of the framework and will run side by side with WF 4.0. This lets you manage the transition at a time that fits your organization's broader goals."
...which is code for, "We know we just screwed up your programming model, but we have a long term strategy, so we hope you will forgive us."
The article goes on to say that
The gains are enormous: custom
activities take center stage, and
authoring them is much simpler;
workflows are entirely declarative;
and there are three workflow flow
styles that you can combine
seamlessly. It's possible that you
could see a 10-fold improvement in the
time required to create and debug
workflows, in addition to 10- to
100-fold runtime performance
improvements.
The change is not without its detractors. In this article at DotNetKicks, the author states that "Microsoft is seriously damaging the Dot Net developer community and adoption in the industry with these half baked product releases and abrupt about-faces after shipping."
Which is why I generally wait for the 2.0 or 3.0 version of Microsoft technologies, although I made an exception for ASP.NET MVC.
We found the workflow product to be difficult to wrap your head around when it came time to pass data in and out. Scott Allen had a series of articles that did a good job describing the process, but still this was not at an easy task.
That's what the word on the street is. And on the internet. 3.0 and 3.5 will be deprecated, but still available.
Is this change not in Visual Studio 2010 beta 1? Download it, find out, and tell Microsoft what you think of it.