Custom component (not control)

[Guest]

I create a custom component, but when I drag and drop in the form, nothing
happens.

Please, help-me.

 

[Tim Wilson]

Does your component look grayed-out in the ToolBox? See the "Adding
Components to the Toolbox" section at the link below.
http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

 

[Guest]

No, my component look not grayed.

Does your component look grayed-out in the ToolBox? See the "Adding
Components to the Toolbox" section at the link below.
http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

 

[Tim Wilson]

What are you expecting to happen when you drag and drop the component? It
should appear in the component tray at the bottom of the design window,
below the Form. Is that not happening? Do you get an exception message of
some sort?

 

[Guest]

I want that component appear in the component tray at the bottom, but when i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.

 

[Tim Wilson]

Can you post the code for your custom component as well as a description of
how you are building the design version?

 

[Guest]

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll /nowarn:1595

 

[Guest]

You wrote :
"You can find this solution attached in a zip file"

Where ??? Do you want my email ?

(e-mail address removed)


Thanks

When I cut and pasted your sample code into a new project, built everything,
and added the component to the ToolBox it all seemed to work ok for me. I
have built a solution that contains a WizardClient project, to test the
component, and a WizardComponent project, that contains the actual component
code. You can find this solution attached in a zip file. I changed a few
things around but it is still the exact concept that you had.

You can build the designer portion of the component through the
"WizardComponent\Designer\Designer.bat" file. However, you will need to
modify the paths to the CF design assemblies, within the designer batch
file, to point to the proper location on your dev machine. Also ensure that
you are running the batch file through the "Visual Studio .NET 2003 Command
Prompt".

Before you open the solution, perform the following actions:
Copy "bin\Debug\Nox.Wizard.dll" to the "<VS.Net 2003 Install
Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE" directory.
Copy "WizardComponent\Designer\Nox.Wizard.Design.dll" to the "<VS.Net 2003
Install Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer" directory.

I noticed that the "NETCFDESIGNTIME" conditional compilation constant was
spelled incorrectly in the code you posted for the Pages property. This
would not cause the issue that you are seeing but it will cause another one
when you are trying to figure out why your component is not "resettable" and
in the correct category.

I also noticed that you were not referencing the AssemblyInfo.cs file in
your designer build. While this shouldn't have caused your problem either,
it, again, could cause version issues since there is a potential that you
could change the run-time version to 1.0 and the design-time version would
still be at 0.0. VS.Net 2003 should still handle everything properly but it
may become a point of confusion for you during maintenance and version
tracking.

Run the solution, in the zip file, and see if everything looks ok. Also, add
the wizard component to the ToolBox using the "Nox.Wizard.Design.dll"
designer assembly, and then drag and drop the component onto the Form to see
if it works as expected. If everything works at your end, then you might
want to go through the source, designer command line, and project properties
to see what is different between my solution and yours.

Let me know how it goes.

--
Tim Wilson
..Net Compact Framework MVP

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll /nowarn:1595

Can you post the code for your custom component as well as a description of
how you are building the design version?

--
Tim Wilson
..Net Compact Framework MVP

I want that component appear in the component tray at the bottom, but when
i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.



:

What are you expecting to happen when you drag and drop the component?
It
should appear in the component tray at the bottom of the design window,
below the Form. Is that not happening? Do you get an exception message
of
some sort?

--
Tim Wilson
..Net Compact Framework MVP

No, my component look not grayed.

:

Does your component look grayed-out in the ToolBox? See the "Adding
Components to the Toolbox" section at the link below.


http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

--
Tim Wilson
..Net Compact Framework MVP

message
I create a custom component, but when I drag and drop in the form,
nothing
happens.

Please, help-me.

 

[Paul G. Tobey [eMVP]]

He posted it to the group, but if you're using a Web-based newsreader, you
may not get it. A real newsreader will show it as an attachment...

Paul T.

You wrote :
"You can find this solution attached in a zip file"

Where ??? Do you want my email ?

(e-mail address removed)


Thanks

When I cut and pasted your sample code into a new project, built
everything,
and added the component to the ToolBox it all seemed to work ok for me. I
have built a solution that contains a WizardClient project, to test the
component, and a WizardComponent project, that contains the actual
component
code. You can find this solution attached in a zip file. I changed a few
things around but it is still the exact concept that you had.

You can build the designer portion of the component through the
"WizardComponent\Designer\Designer.bat" file. However, you will need to
modify the paths to the CF design assemblies, within the designer batch
file, to point to the proper location on your dev machine. Also ensure
that
you are running the batch file through the "Visual Studio .NET 2003
Command
Prompt".

Before you open the solution, perform the following actions:
Copy "bin\Debug\Nox.Wizard.dll" to the "<VS.Net 2003 Install
Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE" directory.
Copy "WizardComponent\Designer\Nox.Wizard.Design.dll" to the "<VS.Net
2003
Install Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer"
directory.

I noticed that the "NETCFDESIGNTIME" conditional compilation constant was
spelled incorrectly in the code you posted for the Pages property. This
would not cause the issue that you are seeing but it will cause another
one
when you are trying to figure out why your component is not "resettable"
and
in the correct category.

I also noticed that you were not referencing the AssemblyInfo.cs file in
your designer build. While this shouldn't have caused your problem
either,
it, again, could cause version issues since there is a potential that you
could change the run-time version to 1.0 and the design-time version
would
still be at 0.0. VS.Net 2003 should still handle everything properly but
it
may become a point of confusion for you during maintenance and version
tracking.

Run the solution, in the zip file, and see if everything looks ok. Also,
add
the wizard component to the ToolBox using the "Nox.Wizard.Design.dll"
designer assembly, and then drag and drop the component onto the Form to
see
if it works as expected. If everything works at your end, then you might
want to go through the source, designer command line, and project
properties
to see what is different between my solution and yours.

Let me know how it goes.

--
Tim Wilson
..Net Compact Framework MVP

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de
programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll /nowarn:1595



:

Can you post the code for your custom component as well as a
description of
how you are building the design version?

--
Tim Wilson
..Net Compact Framework MVP

I want that component appear in the component tray at the bottom,
but when
i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.



:

What are you expecting to happen when you drag and drop the component?
It
should appear in the component tray at the bottom of the design window,
below the Form. Is that not happening? Do you get an exception message
of
some sort?

--
Tim Wilson
..Net Compact Framework MVP

No, my component look not grayed.

:

Does your component look grayed-out in the ToolBox? See the "Adding
Components to the Toolbox" section at the link below.


http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

--
Tim Wilson
..Net Compact Framework MVP

message
I create a custom component, but when I drag and drop in
the form,
nothing
happens.

Please, help-me.

 

[Tim Wilson]

Sorry. Some people can get the attachments and others can't, as Paul stated.
I usually include the code in the message, if it's small and manageable
enough, otherwise I zip it as an attachment so that others may be able to
get the code as well (if possible). I will send it to the email address you
provided.

--
Tim Wilson
..Net Compact Framework MVP

You wrote :
"You can find this solution attached in a zip file"

Where ??? Do you want my email ?

(e-mail address removed)


Thanks

When I cut and pasted your sample code into a new project, built everything,
and added the component to the ToolBox it all seemed to work ok for me. I
have built a solution that contains a WizardClient project, to test the
component, and a WizardComponent project, that contains the actual component
code. You can find this solution attached in a zip file. I changed a few
things around but it is still the exact concept that you had.

You can build the designer portion of the component through the
"WizardComponent\Designer\Designer.bat" file. However, you will need to
modify the paths to the CF design assemblies, within the designer batch
file, to point to the proper location on your dev machine. Also ensure that
you are running the batch file through the "Visual Studio .NET 2003 Command
Prompt".

Before you open the solution, perform the following actions:
Copy "bin\Debug\Nox.Wizard.dll" to the "<VS.Net 2003 Install
Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE" directory.
Copy "WizardComponent\Designer\Nox.Wizard.Design.dll" to the "<VS.Net 2003
Install Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer" directory.

I noticed that the "NETCFDESIGNTIME" conditional compilation constant was
spelled incorrectly in the code you posted for the Pages property. This
would not cause the issue that you are seeing but it will cause another one
when you are trying to figure out why your component is not "resettable" and
in the correct category.

I also noticed that you were not referencing the AssemblyInfo.cs file in
your designer build. While this shouldn't have caused your problem either,
it, again, could cause version issues since there is a potential that you
could change the run-time version to 1.0 and the design-time version would
still be at 0.0. VS.Net 2003 should still handle everything properly but it
may become a point of confusion for you during maintenance and version
tracking.

Run the solution, in the zip file, and see if everything looks ok. Also, add
the wizard component to the ToolBox using the "Nox.Wizard.Design.dll"
designer assembly, and then drag and drop the component onto the Form to see
if it works as expected. If everything works at your end, then you might
want to go through the source, designer command line, and project properties
to see what is different between my solution and yours.

Let me know how it goes.

--
Tim Wilson
..Net Compact Framework MVP

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll /nowarn:1595



:

Can you post the code for your custom component as well as a

description
of

how you are building the design version?

--
Tim Wilson
..Net Compact Framework MVP

I want that component appear in the component tray at the bottom,

but
when

i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.



:

What are you expecting to happen when you drag and drop the component?
It
should appear in the component tray at the bottom of the design window,
below the Form. Is that not happening? Do you get an exception message
of
some sort?

--
Tim Wilson
..Net Compact Framework MVP

No, my component look not grayed.

:

Does your component look grayed-out in the ToolBox? See the "Adding
Components to the Toolbox" section at the link below.

http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

--
Tim Wilson
..Net Compact Framework MVP

message
I create a custom component, but when I drag and drop in

the
form,

nothing
happens.

Please, help-me.

 

[Guest]

Tim

Thank you very much for the aid. It functioned perfectly.
Thanks again, and sorry for my english.

Rogerio

Sorry. Some people can get the attachments and others can't, as Paul stated.
I usually include the code in the message, if it's small and manageable
enough, otherwise I zip it as an attachment so that others may be able to
get the code as well (if possible). I will send it to the email address you
provided.

--
Tim Wilson
..Net Compact Framework MVP

You wrote :
"You can find this solution attached in a zip file"

Where ??? Do you want my email ?

(e-mail address removed)


Thanks

When I cut and pasted your sample code into a new project, built everything,
and added the component to the ToolBox it all seemed to work ok for me. I
have built a solution that contains a WizardClient project, to test the
component, and a WizardComponent project, that contains the actual component
code. You can find this solution attached in a zip file. I changed a few
things around but it is still the exact concept that you had.

You can build the designer portion of the component through the
"WizardComponent\Designer\Designer.bat" file. However, you will need to
modify the paths to the CF design assemblies, within the designer batch
file, to point to the proper location on your dev machine. Also ensure that
you are running the batch file through the "Visual Studio .NET 2003 Command
Prompt".

Before you open the solution, perform the following actions:
Copy "bin\Debug\Nox.Wizard.dll" to the "<VS.Net 2003 Install
Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE" directory.
Copy "WizardComponent\Designer\Nox.Wizard.Design.dll" to the "<VS.Net 2003
Install Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer" directory.

I noticed that the "NETCFDESIGNTIME" conditional compilation constant was
spelled incorrectly in the code you posted for the Pages property. This
would not cause the issue that you are seeing but it will cause another one
when you are trying to figure out why your component is not "resettable" and
in the correct category.

I also noticed that you were not referencing the AssemblyInfo.cs file in
your designer build. While this shouldn't have caused your problem either,
it, again, could cause version issues since there is a potential that you
could change the run-time version to 1.0 and the design-time version would
still be at 0.0. VS.Net 2003 should still handle everything properly but it
may become a point of confusion for you during maintenance and version
tracking.

Run the solution, in the zip file, and see if everything looks ok. Also, add
the wizard component to the ToolBox using the "Nox.Wizard.Design.dll"
designer assembly, and then drag and drop the component onto the Form to see
if it works as expected. If everything works at your end, then you might
want to go through the source, designer command line, and project properties
to see what is different between my solution and yours.

Let me know how it goes.

--
Tim Wilson
..Net Compact Framework MVP

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll
/nowarn:1595



:

Can you post the code for your custom component as well as a description
of
how you are building the design version?

--
Tim Wilson
..Net Compact Framework MVP

I want that component appear in the component tray at the bottom, but
when
i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.



:

What are you expecting to happen when you drag and drop the
component?
It
should appear in the component tray at the bottom of the design
window,
below the Form. Is that not happening? Do you get an exception
message
of
some sort?

--
Tim Wilson
..Net Compact Framework MVP

message
No, my component look not grayed.

:

Does your component look grayed-out in the ToolBox? See the
"Adding
Components to the Toolbox" section at the link below.



http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

--
Tim Wilson
..Net Compact Framework MVP

message
I create a custom component, but when I drag and drop in the
form,
nothing
happens.

Please, help-me.

 

[Tim Wilson]

No problem. Glad to help.

--
Tim Wilson
..Net Compact Framework MVP

Tim

Thank you very much for the aid. It functioned perfectly.
Thanks again, and sorry for my english.

Rogerio

Sorry. Some people can get the attachments and others can't, as Paul stated.
I usually include the code in the message, if it's small and manageable
enough, otherwise I zip it as an attachment so that others may be able to
get the code as well (if possible). I will send it to the email address you
provided.

--
Tim Wilson
..Net Compact Framework MVP

You wrote :
"You can find this solution attached in a zip file"

Where ??? Do you want my email ?

(e-mail address removed)


Thanks



:

When I cut and pasted your sample code into a new project, built everything,
and added the component to the ToolBox it all seemed to work ok for

me.
I

have built a solution that contains a WizardClient project, to test the
component, and a WizardComponent project, that contains the actual component
code. You can find this solution attached in a zip file. I changed a few
things around but it is still the exact concept that you had.

You can build the designer portion of the component through the
"WizardComponent\Designer\Designer.bat" file. However, you will need to
modify the paths to the CF design assemblies, within the designer batch
file, to point to the proper location on your dev machine. Also

ensure
that

you are running the batch file through the "Visual Studio .NET 2003 Command
Prompt".

Before you open the solution, perform the following actions:
Copy "bin\Debug\Nox.Wizard.dll" to the "<VS.Net 2003 Install
Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE" directory.
Copy "WizardComponent\Designer\Nox.Wizard.Design.dll" to the

"<VS.Net
2003

Install Dir>\CompactFrameworkSDK\v1.0.5000\Windows CE\Designer" directory.

I noticed that the "NETCFDESIGNTIME" conditional compilation

constant
was

spelled incorrectly in the code you posted for the Pages property. This
would not cause the issue that you are seeing but it will cause

another
one

when you are trying to figure out why your component is not

"resettable"
and

in the correct category.

I also noticed that you were not referencing the AssemblyInfo.cs file in
your designer build. While this shouldn't have caused your problem either,
it, again, could cause version issues since there is a potential

that
you

could change the run-time version to 1.0 and the design-time version would
still be at 0.0. VS.Net 2003 should still handle everything properly

but
it

may become a point of confusion for you during maintenance and version
tracking.

Run the solution, in the zip file, and see if everything looks ok.

Also,
add

the wizard component to the ToolBox using the "Nox.Wizard.Design.dll"
designer assembly, and then drag and drop the component onto the

Form to
see

if it works as expected. If everything works at your end, then you might
want to go through the source, designer command line, and project properties
to see what is different between my solution and yours.

Let me know how it goes.

--
Tim Wilson
..Net Compact Framework MVP

using System;
using System.Data;
using System.ComponentModel;

#if NETCFDESIGNTIME
[assembly: System.CF.Design.RuntimeAssemblyAttribute("Wizard,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null")]
#endif


namespace Nox
{
#if NETCFDESIGNTIME
[ToolboxItemFilter("System.CF.Windows.Forms",
ToolboxItemFilterType.Custom)]
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
#endif

/// <summary>
/// Summary description for Wizard.
/// </summary>
public class Wizard: Component
{
#if NETCFDESIGTIME
[System.ComponentModel.Category("Wizard")]
[System.ComponentModel.DefaultValueAttribute(5]
#endif

private int _Pages;
public int Pages
{
get {return _Pages;}
set {_Pages = value;}
}

public Wizard()
{
}
}
}


DLL Design

@csc /noconfig /define:NETCFDESIGNTIME /target:library
/out:design.Wizard.dll Wizard.cs /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Design.dll" /r:"C:\Arquivos de programas\Microsoft
Visual Studio .NET 2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Windows.Forms.dll" /r:"C:\Arquivos de
programas\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows
CE\Designer\System.CF.Drawing.dll"
/r:System.Windows.Forms.dll /r:System.Drawing.dll /r:System.dll
/r:System.XML.dll /r:System.Web.Services.dll /r:System.Data.dll
/nowarn:1595



:

Can you post the code for your custom component as well as a description
of
how you are building the design version?

--
Tim Wilson
..Net Compact Framework MVP

I want that component appear in the component tray at the

bottom,
but

when
i
drag and drop this no happens. No message or exception are show.

I sorry, but my english is not good.



:

What are you expecting to happen when you drag and drop the
component?
It
should appear in the component tray at the bottom of the design
window,
below the Form. Is that not happening? Do you get an exception
message
of
some sort?

--
Tim Wilson
..Net Compact Framework MVP

message
No, my component look not grayed.

:

Does your component look grayed-out in the ToolBox? See the
"Adding
Components to the Toolbox" section at the link below.

http://msdn.microsoft.com/library/d..._evtuv/html/etconcustomcontroldevelopment.asp

--
Tim Wilson
..Net Compact Framework MVP

"Rogerio Jun" <[email protected]>

wrote
in

message
I create a custom component, but when I drag and drop

in
the

form,
nothing
happens.

Please, help-me.