Project Properties

Error: There was an error trying to load project properties window. Close the window and try again.
Object reference not to an instance of an object.

If you have this error and you can't load project properties and etc... Don’t worry! Because you have chance for continue your tasks without solving this error.
For example if you want to change your application's icon you must edit a XML base file in an editor (like notepad).
Go to your project directory and open [projectname].csproj (for example like WindowsApplication1.csproj) in notepad or any simple text editor.
You can see a part of a TEXT in XML format like below:

<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition="'$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition="'$(Platform)' == '' ">AnyCPU</Platform>
<ProductVersion>8.0.40607</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{CDBB5C9E-C36D-489B-A538-6FD750DE8CBC}</ProjectGuid>
<OutputType>WinExe</OutputType>
<RootNamespace>WindowsApplication1</RootNamespace>
<AssemblyName>WindowsApplication1</AssemblyName>
<WarningLevel>4</WarningLevel>
<ApplicationIcon>app.ico</ApplicationIcon>
...

You can see the <ApplicationIcon>app.ico</ApplicationIcon> that can solve your Application Icon problem without loading the project properties page.
This XML file is so simple and you can solve more other problems with a little search;-)
After that, you must load your solution and compile it again.
This method is for Visual Studio Project 2005 (Whidbey) but absolutely can used for VSP2002 and VSP2003 and VSP2005Beta2 and I think that can be also used for Orcas (next generation of Visual Studio)
The mentioned points are for C# project but absolutely not different for VB.Net, J# and other .Net projects.

Metro

If you want to release a new version of your "printer driver" or you are a "printer driver developer" there is the Microsoft newest technology. I'm so glad to tell you that "Metro Print Path" is a newest technology print path for document that is so closed to the Avalon graphics engine. Metro Print Path is a print path that will be put in the next client version of Microsoft® Windows® (Longhorn).
Metro uses the most of the newest technology such as XML, Unicode, ZIP and etc all together.
In a word METRO is An advanced print format such as Adobe PDF and more that.
The METRO enhancements the printer driver architecture and the New print paths from the application to the printer.
Among the benefits that the new architecture is expected to provide are:
• Improved performance
• Support for extended color spaces
• Improved fidelity (providing an efficient printing pipeline for handling advanced graphics such as transparency and smooth gradients)
• Integrated document security (incorporating support for digital signatures)
• Enhanced user experience
If you have questions about the Metro print path send e-mail to prninfo@microsoft.com.

PS1: Sample MetroDrv driver code is planned for Longhorn Beta 2.
PS2: A draft version of the Metro format specification is planned for publication early in 2Q2005.
PS3: The metro print path does not support Postscript pass through
PS4: Microsoft provide a framework for applications to access or share private printer settings.
PS5: Microsoft resolve the plotter form size limitation in the Metro print path.
PS6: Microsoft provide a reference implementation for a Metro raster image processor (RIP).

[doc] Metro_FAQ.doc: http://download.microsoft.com/download/5/D/6/5D6EAF2B-7DDF-476B-93DC-7CF0072878E6/metro_FAQ.doc
[doc] Metro_support.doc: http://download.microsoft.com/download/5/d/6/5d6eaf2b-7ddf-476b-93dc-7cf0072878e6/Metro_support.doc
[link] Windows Printing Architecture and Driver Support: http://www.microsoft.com/whdc/device/print/default.mspx
[link] Metro format specification: http://www.microsoft.com/whdc/device/print/metro.mspx
[link] Metro FAQ page: http://www.microsoft.com/whdc/device/print/metro_FAQ.mspx
[link] Office Online File Converters and Viewers: http://office.microsoft.com/en-us/assistance/HA010449811033.aspx
[link] WinHEC 2005 Conference Presentations and Papers: http://www.microsoft.com/whdc/winhec/papers05.mspx
[link] My favorite page about Windows Driver Foundation: http://www.microsoft.com/whdc/driver/wdf/default.mspx

شاید به فارسی خیلی نشه چیز زیادی گفت جز اینکه وقتی شنیدم Adobe داره Macromedia رو می خره حس کردم که احتمالا باز یه خبری شده. آره باز این مایکروسافت افتاده به جون این شرکت ها و این بار داره پوزه PDF رو به خاک می ماله.
البته باید واستاد و دید چون جدیدا مایکروسافت مثل بیل خیلی پیر شده و سخت می تونه حال این و اون رو بگیره .. نمونش همین گوگول، iPod و چند تا چیز کوچولوی دیگه.
از صمیم قلب امیدوارم که این بار بیلی از صندوقش چیز معرکه تری بیرون بیاره نه مثل XP.

Convert from byte[] to string

Do you have this compilering error message?
"Argument '?': cannot convert from 'byte[]' to 'string' ???.cs" with .Net Compiler .Net 1.0 or .Net 2..0?
Do you have any problem for converting between 'byte[]' to 'string' (from 'byte[]' to 'string' or from 'string' to 'byte[]')?
Ok! Don’t worry.
You can use Encoding class (library).

In this example ABC is the name of a project and A01 is a resource with byte[] format.

String strTest = Encoding.ASCII.GetString(ABC.Properties.Resources.A01);
Byte[] bytTest = Encoding.ASCII.GetBytes(strTest);

So easy! Yes?

عجیبه باز یادم رفت که باید تو این دات نت همش از انکدینگ و دیکدینگ استفاده کنیم.
دوتا مثال بالا مثل روز راه رو نشون میده (یه چیزی هم روش!!!)

Verbs in C# Whidbey

Error: Verbs Error: no suitable method found to override.
If you have the "public override DesignerVerbCollection Verbs" problem in your UserControl's Class (in C# 2.0 or C# 2005) then you must use an "internal class" of "ControlDesigner" similar to your UserControl's class because the UserControl dose not contain the Verbs property and the "public override DesignerVerbCollection Verbs" can't accept the override method.
The brilliant way to insert a new item in the Actions Menu in the design mode for your UserControl(s) is to use the "internal class" after your UserControl class.

For example:

internal class MyControlDesigner : System.Windows.Forms.Design.ControlDesigner
{
    private DesignerVerbCollection m_pVerbs = new DesignerVerbCollection();
    public override System.ComponentModel.Design.DesignerVerbCollection Verbs
    {
        get
        {
            if (m_pVerbs.Count < 1)
            {
                m_pVerbs.Add(new DesignerVerb("About", new EventHandler(this.heoAbout_Click)));
            }
            return m_pVerbs;
        }
    }
    private void heoAbout_Click(object sender, EventArgs e)
    {
        MessageBox.Show("You're Successful");
    }
}

But this is important that you must show this class to the Runtime Designer, with like this code:
[Designer(typeof(MyControlDesigner))]
You must put this code to top of your master UserControl class.
Please, attention to this: System.Windows.Forms.Design
If you don't have this reference in your Project's References you must add it.

خب راستش بدجوری تو گل گیر کرده بودم تا اینکه راهش پیدا شد. یک پروژه تو 2003 را به 2005 بیارید و بعد از Convert شدن خوب بررسیش کنید. اصولا اغلب تغییرات رو می شه از همین روش پیدا نمود البته تا زمانی که یه help درست حسابی براش بیاد. اگه متن بالا رو هم بخونید متوجه می شوید که چه راحت می شه یک Verb override نوشت تازه کلی هم به کلاس برنامه اضافه می شه :)) خوش باشید.