|
Setting the Anchor property of the controls to none will solve it. 
|
|
|
|
|
hi all
i derived a class from DataGridViewTextBoxColumn named DataGridViewTextBoxColumn2
public class DataGridViewTextBoxColumn2 : DataGridViewTextBoxColumn<br />
{<br />
[DefaultValue(typeof(bool), "true")]<br />
public bool IsMandatoryColumn<br />
{ get; set; }<br />
}<br />
in design time i click the Edit and change the value IsMandatoryColumn to true
but when i return to edit form to chock if the property set to true or not surprisingly i find this property with the value of False
please help me
by the way i tried to implement a constructor and set the default value there
and also tried to change the access method to old form of
<br />
get{return ...}<br />
set{...=value}<br />
but the problem still persists
pleeeeeeeeeeaaaaaaaaaaaaaaaaaase help me before i gonna crazy  
|
|
|
|
|
hi
the answer is Pretty simple
public class DataGridViewTextBoxColumn2 : DataGridViewTextBoxColumn<br />
{<br />
[DefaultValue(typeof(bool), "false")]<br />
public bool IsMandatoryColumn<br />
{ get; set; }<br />
<br />
public override object Clone()<br />
{<br />
DataGridViewTextBoxColumn2 test = (DataGridViewTextBoxColumn2)base.Clone();<br />
test.IsMandatoryColumn = this.IsMandatoryColumn;<br />
return test;<br />
}<br />
}<br />
i love internet 
|
|
|
|
|
The response you've got before is going to work, anyhow I think that you need to know why this won't work.
Thing is that DefaultValue, prevents the form's designer from generating code for this property. So when you set the property as true, no value is generated and bool variables always initialize to false.
That's what's giving you trouble.
|
|
|
|
|
hi dear gonzalo
NO
i used DefaultValue intentionally to prevent designer from generating this line of code
there is no different from having DefaultValue or not (i tried this senario several times) and it does not work.
i seams designer will clone the object and copy all the changed properties and i have to copy may new property implicitly.
|
|
|
|
|
Anyone has an example or resource on how to post to LinkedIn using C#?
|
|
|
|
|
Try this, looks like there is an API
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi,
I'm experimenting with a Web Service, using .NET 2.0 and IIS7. This is the entire Web Service source (demo1.asmx):
<%@ WebService Language="C#" Class="Demo1ns.Demo1class" %>
using System;
using System.Web.Services;
namespace Demo1ns {
[WebService (Name="Demo1", Description="Test color result")]
public class Demo1class {
[WebMethod (Description="Get a size")]
public System.Drawing.Size GetSize() {
return new System.Drawing.Size(12,34);
}
[WebMethod (Description="Get a color")]
public System.Drawing.Color GetColor() {
return System.Drawing.Color.Yellow;
}
}
}
Browsing to http://localhost/services/Demo1.asmx I get the web page presenting both methods. Invoking the first works fine as it returns:
<Size>
<Width>12</Width>
<Height>34</Height>
</Size>
However the GetColor method (both variants) fails and simply returns:
<Color/>
whatever I try, a Color is never returned.
So why is it handling Size and not Color, both are pretty much similar structs. How does one fix this?
|
|
|
|
|
Ummm... because the XmlSerializer doesn't know how you want it serialized?
What would you like?
Have you tried -- "#" + System.Drawing.Color.Yellow.ToArgb().ToString ("X8")
or similar?
Or you could use -- System.Drawing.Color.Yellow.ToKnownColor()
|
|
|
|
|
I'm new to the whole Xml and WebService things. I managed to transfer lots of types including structs (such as Size) and DateTime, without worrying about formatting. In what I'm after Color is the only problem, I don't really care how it arrives at the client as all structs become class instances anyway on the client side (the Size struct becomes a Size-like class with a Width and a Height member), so if I want to use them as CLR types, I need to convert them anyway.
So please show me the simplest magic that gives me say the ARGB value, or something similar while keeping the server-side code simple (I don't want to add method calls everywhere (there are multiple color returns throughout the code, sometimes inside a result struct) if I can avoid it, otherwise I would have communicated the ToArgb() result.
TIA
|
|
|
|
|
You needs codez? Sounds Urgentz. 
Just for the heck of it, I was just playing around with a Color wrapper class, with decent results.
[System.SerializableAttribute()]
public class Color : System.Xml.Serialization.IXmlSerializable
{
private static readonly System.Text.RegularExpressions.Regex reg ;
static Color
(
)
{
reg = new System.Text.RegularExpressions.Regex
(
@"^\#(?'Digits'[0-F]{8})$"
,
System.Text.RegularExpressions.RegexOptions.IgnoreCase
) ;
return ;
}
public System.Drawing.Color color { get ; set ; }
public System.Xml.Schema.XmlSchema
GetSchema
(
)
{
return ( null ) ;
}
public void
WriteXml
(
System.Xml.XmlWriter Writer
)
{
Writer.WriteString ( "#" + this.color.ToArgb().ToString ( "X8" ) ) ;
return ;
}
public void
ReadXml
(
System.Xml.XmlReader Reader
)
{
System.Text.RegularExpressions.MatchCollection mat =
reg.Matches ( Reader.ReadString() ) ;
if ( mat.Count == 1 )
{
int i ;
if
(
System.Int32.TryParse
(
mat [ 0 ].Groups [ "Digits" ].Value
,
System.Globalization.NumberStyles.HexNumber
,
null
,
out i
)
)
{
this.color = System.Drawing.Color.FromArgb ( i ) ;
}
}
return ;
}
}
I'm think of adding implicit conversions to it (and making the field private).
I probably won't be able to respond again until tomorrow afternoon (UTC -7:00).
|
|
|
|
|
wow. I was hoping for a magic attribute of some kind, and you offer 70+ lines of code. It will be a while before I have digested that.
Thanks.
|
|
|
|
|
What's a line?
Besides, maybe I'll need it someday.
If you like it, please send chocolate. 
|
|
|
|
|
PIEBALDconsult wrote: What's a line?
When you have some amount of text, anything that sits between the beginning and the end gets chopped into smaller amounts (called "lines") either by newlines (you know them well) or by wrapping (you may be unfamiliar with that phenomenon).
PIEBALDconsult wrote: If you like it, please send chocolate
I would like it a lot if the deserializer method would get transferred automatically from server to client, just like the data members are when using WSDL.EXE to obtain the proxy class. Unfortunately only data members get through, as Keith stated.
PIEBALDconsult wrote: please send chocolate
I'll try some first, just to make sure.
Thanks again for your input.
|
|
|
|
|
The XML you transfer in web service calls are pretty much just bags of data that allow you to populate objects at either end. Unfortunately this is hidden from the outset in the .net framework tools. For example, you can create a "proper" object with methods, but these are lost on the client side if you just use the generated proxy classes the messages are deserialized into (at least not without extra developer jiggery-pokery).
Web services should theoretically be interoperable (e.g. a Java/ C++ clients should be able to call a .net web-service) if the Color object was directly serializable across the web service it would break this pattern as it is specific to .net. You have two [easy] ways to handle your problem: send the hex colour value as a string or (better) convert it to an integer. Obviously this will involve a little work to re-create the System.Color value.
|
|
|
|
|
Keith Barrow wrote: developer jiggery-pokery
One of my favorite things. 
Edit:
Keith Barrow wrote: if you just use the generated proxy classes
So don't do that.
modified on Saturday, September 25, 2010 1:14 PM
|
|
|
|
|
Yes, in the mean time I discovered no methods make it across when using WSDL.EXE, all the client gets for free is a little class with data members (which is great by itself). As MSDN isn't very informative on jiggery-pokery (I myself am not familiar with such techniques) I'll probably go for the ToArgb() approach.
Many thanks for the information.
|
|
|
|
|
That's up to the client.
I was playing around with WCF last April/May and didn't have such trouble. It helped that the client is in the same solution as the server, but that isn't necessary.
I've been meaning to get back to that; I'll see if there are any snippets I can send to demonstrate what I did.
Here's a quick little diagram based on my recollections:
|------------------|
| Client |
|------------------|
| |
| | <-- (Jiggery pokery happens here, but it's perfectly valid)
|---------| |
| Service | |
|---------| |
| |
| |
|------------------|
| Classes in a DLL |
|------------------|
|
|
|
|
|
OK, let me provide some context. I'm preparing a proposal specification for a CodeProject Web Service, something that would provide information about members, articles, messages, etc, so several existing and future applications (such as CP Vanity) could use it to their advantage, which would be much preferred over fetching web pages and scraping HTML. The proposal would be discussed amongst interested members before Chris might commit to it and implement it.
I expect the CP data model (as well as the subset we want access to) will evolve just like anything else, and I do want future old clients not to break under future new service versions. So I'm looking for a simple data model and a reliable communication protocol. I'm rather pleased with what IIS and WSDL are offering, as it works perfectly for basic types such as int, float, bool, string, as well as DateTime; it works pretty well for Size too.
FYI: WSDL.EXE is a utility that interrogates the service (using WSDL, an XML-based language) and creates a proxy class to be used by the client.
I mainly see two shortcomings:
1.
Color does not get through by default; it needs extra code at both ends. The extra code (e.g. client-side deserialization) cannot be transmitted automatically by WSDL, so there is a risk for future compatibility problems.
Color sure isn't the only type that wouldn't get across, however from the types I think we need, it is the only one that fails.
2.
Everything that was a class or struct at the server side becomes a class (never a struct) of a different type at the client. So one can send a System.Graphics.Size without any problem, but one gets a lookalike class instance at the client, so when a real System.Graphics.Size is required, one must recreate it. No big deal, just not very elegant.
I welcome your thoughts.
|
|
|
|
|
Luc Pattyn wrote: WSDL.EXE
For my experimentation last spring I used: svcutil http://localhost:8000/junkyard?wsdl /out:JunkyardClient.cs /noconfig
which creates the proxy class file (JunkyardClient.cs). I then wrap the proxy class in another class and add other stuff:
public class JunkyardProxy : JunkyardClient , Junk.Types.IJunkyard
The Client then uses that class:
using
(
Junk.Types.IJunkyard junk
=
new Junk.Types.JunkyardProxy()
)
{
|
|
|
|
|
I'm not familiar with svcutil.
Your example with WSDL would be WSDL http://localhost:8000/junkyard
but then maybe svcutil has some options that could be useful. I'll have to check that.
And yeah, I started thinking along such lines too, extending the proxy class. Chances are the wrapper class itself can be small and pretty stable as it probably only offers some utilitarian methods (one might consider using extension methods nowadays) regarding a few stubborn CLR types that don't get across properly without some help.
Are you using any reflection in your wrapper? Did you publish an actual article or example somewhere, something I could/should read?
Thanks.
|
|
|
|
|
Luc Pattyn wrote: Are you using any reflection in your wrapper?
Not at this time.
Luc Pattyn wrote: extending the proxy class
I was happily surprised that some of the generated classes are partial. If they all were I could simply add more partial code rather than wrap the classes.
Luc Pattyn wrote: Did you publish an actual article or example somewhere, something I could/should read?
I was going to, but I was in school all June/July and then got a job in August so until today I hadn't touched this stuff since May. I was thinking of writing "How to a write WCF Web Service the PIEBALD way" -- it's kinda funny that the test client outputs "Hello, World".
Anyway, I'll see about passing a color (colour) through this thing, see what happens, and let you know.
|
|
|
|
|
Great. Thanks a lot.
|
|
|
|
|
DAGNABIT!!
Microsoft hates me sucks today!
Without the Colour property, the service works just fine, the proxy file begins this way:
namespace Junk.Types
{
using System.Runtime.Serialization;
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.CodeDom.Compiler.GeneratedCodeAttribute("System.Runtime.Serialization", "4.0.0.0")]
[System.Runtime.Serialization.DataContractAttribute(Name="Record", Namespace="http://schemas.datacontract.org/2004/07/Junk.Types")]
public partial class Record : object, System.Runtime.Serialization.IExtensibleDataObject
::snip::
With the Colour property, the proxy file is totally different:
using System.Data;
::snip::
/// <remarks/>
[System.CodeDom.Compiler.GeneratedCodeAttribute("svcutil", "4.0.30319.1")]
[System.SerializableAttribute()]
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.ComponentModel.DesignerCategoryAttribute("code")]
[System.Xml.Serialization.XmlTypeAttribute(Namespace="http://schemas.datacontract.org/2004/07/Junk.Types")]
public partial class Record
{
private System.Data.DataSet favouriteColourField;
::snip::
/// <remarks/>
[System.Xml.Serialization.XmlElementAttribute(IsNullable=true, Order=0)]
public System.Data.DataSet FavouriteColour
{
get
{
return this.favouriteColourField;
}
set
{
this.favouriteColourField = value;
}
}
::snip::
The Record class is no longer in the Junk.Types namespace! And other problems as well.
Maybe I should try it as a Color...
|
|
|
|
|
Hmm. I did get a DataSet at some point from WSDL.EXE too. And I didn't like it a bit.
I still have a lot to explore, I'm not giving in yet!
BTW: Keith Barrow just added quite a message to this thread, you might be interested as well.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
