Search Results

Search found 79 results on 4 pages for 'abatishchev'.

Page 4/4 | < Previous Page | 1 2 3 4 

• Wherewith replace Dictionary.Where(p => p.Key is T)

  - by abatishchev

  I have a System.Collections.Generic.Dictionary<System.Web.UI.Control, object> where all keys can be either type of System.Web.UI.WebControls.HyperLink or type of System.Web.UI.WebControls.Label. I want to change Text property of each control. Because HyperLink doesn't implement (why??) ITextControl, I need to cast Label or HyperLink explicitly: Dictionary<Control,object> dic = .. dic .Where(p => p.Key is HyperLink) .ForEach(c => ((HyperLink)c).Text = "something") dic .Where(p => p.Key is Label) .ForEach(c => ((Label)c).Text = "something") Are there ways to workaround such approach?

  Read the article

• Is read-only auto-imlemented property possible?

  - by abatishchev

  Hello. I found a topic on MSDN that talks that yes, this is possible. I did a test that seems to break this statement: using System; namespace Test { class Program { static void Main(string[] args) { Foo f = new Foo("1"); Console.WriteLine(f.Bar); // prints 1 f.Test("2"); Console.WriteLine(f.Bar);// successfully prints 2 } } class Foo { public Foo(string b) { this.Bar = b; } public string Bar { get; private set; } public void Test(string b) { // this would be impossible for readonly field! // next error would be occur: CS0191 or CS0191 // A readonly field cannot be assigned to (except in a constructor or a variable initializer) this.Bar = b; } } } Where am I wrong?

  Read the article

• Why "\d+{1,4}(?:[.,]\d{1,4})?" in RegularExpressionValidator throws Exception: "Nested quantifier {"

  - by abatishchev

  I have asp:RegularExpressionValidator with ValidationExpression="\d+{1,4}(?:[.,]\d{1,4})?" but it doesn't' work, parser throws ArgumentException: parsing "\d+{1,4}(?:[.,]\d{1,4})?" - Nested quantifier {. Where is my mistake? I want to allow strings like xxxx,xxxx - from 1 to 4 digits and decimal digits are not required, e.g.: 1000, 99,99, 0,2498, etc.

  Read the article

• NullDisplayText in markup vs ISNULL(field, 0) in SQL?

  - by abatishchev

  Which approach is better to use: BoundField.NullDisplayText isn't set. NULL-case is foreseen in SQL query, i.e. SELECT ISNULL(amount, 0) FROM table or BoundField.NullDisplayText is set, e.g. "0.00 %". NULL-case isn't foreseen in SQL query, i.e. SELECT amount FROM table What do you think?

  Read the article

< Previous Page | 1 2 3 4