MSDN Magazine June 2004
View Complete Post
This is the second of two articles discussing the extremely rich design-time features of the .NET Framework. Part 1 discussed the basics, showing you where to start and how to extend your control implementation through attributes and interfaces, as well as their effects on the property browser, code serialization, and other controls. Part 2 continues the journey by concentrating on design-time functionality that you can implement beyond your components and controls, including TypeConverters, UITypeEditors, and Designers. It would be impossible to cover everything you can do in two short articles, which is a testament to just how all-encompassing and flexible the design-time capability of the .NET Framework is.
Michael Weinhardt and Chris Sells
MSDN Magazine May 2003
Visual Studio .NET provides support for designing rich features into your controls and components, allowing you to set properties, set form placement, inherit from base classes, and much more. So how does Visual Studio .NET do all this? What does the Windows Forms designer do? What's the difference between a control and a component? How does Visual Studio integrate your controls so that they can access features of the .NET Framework?In this article, the authors answer these common questions by building a clock control and taking the reader along for the ride. In building the control, hosts and containers are illustrated, the property browser is explained, debugging is discussed, and a general overview of the design-time infrastructure is presented.
MSDN Magazine April 2003
The Microsoft .NET platform provides you with a rich set of services for building profilers and application monitors for applications targeting the Common Language Runtime (CLR). These services expose runtime events that occur during the execution of a .NET application. They can be used to obtain information about managed code being executed under the runtime. This article describes the .NET CLR Profiling Services and shows how to use the services to build a simple profiler that will provide hot spot information for any .NET application. The sample profiler can easily be modified to suit other profiling and monitoring needs.
MSDN Magazine November 2001
MSDN Magazine August 2000
OS: Windows2008 x86
I have developed a 30 concurrent user performance test comparing the performance of WCF versus web service. The test applications are identical except for WCF/web service calls.
The web service massively out performs WCF: average web service call 400MS, WCF 2250MS during the test.
Are there any configuration parameters that would constrict WCF performance?
I changed the WCF web.config as follows:
I have a Winforms app (VS 2005/DotNet2) that contains a generic collection of a user control
- Private c as new collection(of UserControl1)
Essentially it's the heart of the system and the system has grown extremely fat, to the point where users are complaining about speed. Aside from the large number of database lookups, a major part of operations is iterating through the collection itself,
to create it, set its values, and so forth. (I am planning to try performance tools but that may take some time.)
For starters I was wondering if there was anything more optimum than a
For each UC1 in C loop? I really haven't worked that much with generic collections other than this one instance.
Any recommendation or is there best practices for environment where you have heavy users from other countries connect to sharepoint farm in US without having another SP farm setup with replication in those sites?
I was looking at office Office Groove (now Workspace) but that is only good for doclib and such right? Let's say I have a huge page with gantt view, this won't work.
Thanks for any feedback