Basic and easy .NET 2.0 control to make your application feel like MS Office 2007 UI experience.
Download mentas Ribbon
Tuesday, June 27, 2006
A free charting library for .NET
ZedGraph is a set of classes, written in C#, for creating 2D line and bar graphs of arbitrary datasets. The classes provide a high degree of flexibility - almost every aspect of the graph can be user-modified. At the same time, usage of the classes is kept simple by providing default values for all of the graph attributes. The classes include code for choosing appropriate scale ranges and step sizes based on the range of data values being plotted.
ZedGraph also includes a UserControl interface, allowing drag and drop editing within the Visual Studio forms editor, plus access from other languages such as C++ and VB.
Example charts generated with ZedGraph
TopMost Form
"A topmost form is a form that overlaps all the other (non-topmost) forms even if
it is not the active or foreground form. Topmost forms are always displayed at
the highest point in the z-order of the windows on the desktop. You can use this
property to create a form that is always displayed in your application,
such as a Find and Replace tool window."
The well known issue that the TopMost Form stealing focus ...
The fallowing code can solve the problem.
private const int SW_SHOWNA = 8;
private const int SW_SHOWNA = 8;
[DllImport("user32", CharSet = CharSet.Auto)]
private extern static int ShowWindow( IntPtr hWindow, int nCmd );
public void MakeTopMostForm(Form frm)
{
ShowWindow(frm.Handle, SW_SHOWNA);
}
Sunday, June 25, 2006
BytesRoad.NetSuit Library 2.0
BytesRoad.NetSuit Library 2.0 is a free network library for .NET platform distributed under GNU General Public License. The library is written in C# language and source codes are also available.
FTP functionality is exposed by FtpClient class . This class contains high level methods that allow you to communicate with FTP server. Also available SocketEx class. This class may be used instead of the .NET Framework's Socket class wish your application to be able to communicate through the proxies (Socks4, Socks5 etc).
FTP Implementation features
- Fully compliant with RFC 959 (File Transfer Protocol) and related documents
- Comprehensive reference for the component (as compiled HTML file) integrated with .NET Framework SDK v1.1 help
- Support communication with FTP server through the proxies. Following proxies are currently supported:
- Socks4
- Socks4a
- Socks5, username/password authentication method supported
- Web proxy (HTTP CONNECT method), basic authentication method supported
- All methods requiring networking hava synchronous and asynchronous versions
- Implementation of asynchronous methods follows .NET Asynchronous methods pattern
- Each operation may be configured with required time out period
- "Store unique file" command can be customized by specifying regular expression
- Directory listing parser supports common directory listing formats and can be customized by the user-defined parser
- Exception oriented error handling
- Provide events for monitoring the communication process:
- Event during data transferring
- Event during receiving ftp items
- Event on each FTP command sent
- Event on each FTP response received
- Supported on .NET Framework v1.0 and later
Sockets implementation features
- Comprehensive reference for the component (as compiled HTML file) integrated with .NET Framework SDK v1.1 help
- Following proxies are currently supported:
- Socks4
- Socks4a
- Socks5, username/password authentication method supported
- Web proxy (HTTP CONNECT method), basic authentication method supported
- All methods requiring networking have synchronous and asynchronous versions
- Implementation of asynchronous methods follows .NET Asynchronous methods pattern
- Each operation may be configured with required time out period
- Exception oriented error handling
- Supported on .NET Framework v1.0 and later
Wednesday, June 21, 2006
Free SharePoint 2007 Book
"Future or current SharePoint developers should at least flip through the book to build a picture of how MOSS 2007 fits together and what the concepts are -- changes to the security model, site definitions, site features, Content Types, how Workflow is integrated, Excel Services -- there are a hundred small topics, you owe it to yourself to get a handle on the big picture."
Table of Contents
- Microsoft Windows SharePoint Services 3.0
- Building Solutions with Office SharePoint Server 2007
- Building a Basic SharePoint Site
- Organizing List and Documents with Site Columns and Content Types
- Working with Features in Windows SharePoint Services
- Windows SharePoint Services Core Development
- Creating Workflows: The Missing Piece of Office Productivity
- Introducing Excel Services
- Microsoft Office InfoPath 2007 and Microsoft Office Forms Server 2007
[Via Roy Osherove's Blog]
Wednesday, June 14, 2006
Creating clonable menu items in .Net 2.0 ( Implementing CloneMenu method )
In Windows Forms FAQ( .Net 2.0) I found that the CloneMenu method is not implemented ...:-(
"With the entire ToolStrip family of controls we do not have an integrated commanding
architecture nor do we support cloning of items to appear in multiple places.
We do support reusing the same ToolStripDropDown or ContextMenuStrip in multiple places (non-nested).
We understand this may require more state management and maintenance code and are looking
at ways to improve this in the future.
Erick Ellis, 6 January 2005 # (MS)"
Here's "fast and dirty" solution:
using System;
using System.Collections.Generic;
using System.Text;
using System.Windows.Forms;
namespace WindowsApplication66
{
class CloneToolStripLabel:ToolStripLabel
{
public CloneToolStripLabel( string text )
: base(text)
{
}
public CloneToolStripLabel CloneMenu()
{
return ( CloneToolStripLabel )this.MemberwiseClone();
}
}
}
Usage:
CloneToolStripLabel menuItem = new CloneToolStripLabel("Kuku");
toolStrip1.Items.Add(menuItem);
toolStrip2.Items.Add(menuItem.CloneMenu());
Also you can read this post
Sunday, June 11, 2006
Save and restore the size,location and state of a Windows Form in .NET 2.0
The fallowing example saves the properties (location, size and windows state) of a form to app.config
when the form is closed and restores the form state when it is loaded.
Create three properties called Size ,Location and WindowState in project settings dialog as shown in picture:
to place form correctly on a multi screen desktop )
private void Form1_Load( object sender, EventArgs e )
{
// restore location and size of the form on the desktop
this.DesktopBounds =
new Rectangle(Properties.Settings.Default.Location,
Properties.Settings.Default.Size);
// restore form's window state
this.WindowState = ( FormWindowState )Enum.Parse(
typeof(FormWindowState),
Properties.Settings.Default.WindowState);
}
private void Form1_FormClosing( object sender, FormClosingEventArgs e )
{
Properties.Settings.Default.Location = this.DesktopBounds.Location;
Properties.Settings.Default.Size = this.DesktopBounds.Size;
Properties.Settings.Default.WindowState =
Enum.GetName(typeof(FormWindowState), this.WindowState);
// persist location ,size and window state of the form on the desktop
Properties.Settings.Default.Save();
}
Saturday, June 10, 2006
PowerShell Editor and IDE.
PowerShellIDE is the PowerShell Editor and IDE.
It is a graphical user interface that helps explore and exploit the vast power available with PowerShell. It contains a debugger, lets you step through PowerShell scripts, explore variables as you run your scripts and also supports many Intellisense-like functions.
MSBuild Sidekick
MSBuild Sidekick is a GUI application for creating and editing build project files for Microsoft Build engine. The application provides full-fledged graphic user interface as alternative to editing build project files by hand. The full range of MSBuild schema elements is supported.
MSBuild Sidekick features:
- Load and modify any file complying to MSBuild schema
- View build project structure in a tree view that displays tasks used in build, property groups and properties, item groups and items, targets and targets tasks and imported build projects.
- Show or hide presentation of imported definitions in a project tree view
- View MSBuild project raw XML source as you modify the project
- Modify project default targets
- Add or remove tasks used in build project from external assembly
- Add, remove or modify property groups
- Add, remove or modify properties in property groups
- Add, remove or modify item groups
- Add, remove or modify items in item groups
- Add, remove or modify targets
- Add, remove or modify selected target's tasks, tasks order
- Modify selected task properties (including output properties specification)
- Import or remove external build projects
- Open any imported project from the loaded project
[Via Larkware News]
Thursday, June 01, 2006
How to prevent the UserControl class to appear in the Visual Studio toolbox
You can prevent the UserControl class to appear in the Visual Studio toolbox by adding fallowing attribute to it
[System.ComponentModel.ToolboxItem(false)]
Remember that this attribute is inheritable ,so derived UserControls must place have a System.ComponentModel.ToolboxItem(false) attribute if they want to be available on the Visual Studio toolbox .
Subscribe to:
Posts (Atom)
