Windows 10: 20966 error: variable must be of type "object".

20966 file "c:\programdata\realtekHd\taskhost.exe": error: variable must be of type "object".

:)

 

System environment variable won't stick

Running Win10 Home on an Acer Spin 3, 64bit, i7cpu. I try to add a path to the system environment variables by:

1. Control Panel > System > Advanced system settings > Advanced tab > Environment variables

2. The "Environment Variables" window opens.
3. In the "System Variables" pane I select "Path" and click the EDIT button.
4. A list of the current system paths is displayed.
5. I click the NEW button, browse to the path I want to add which is "C:\Python36-32" and click OK. The path "C:\Python36-32" is added to the list of current system paths.
6. I click OK and am returned to the "Environment Variables" window.
7. I click the "X" at the top right to close the "Environment Variables" window.

Now if I click the "Environment Variables" button again (end of step-1) and repeat steps 2-4, the new path I added in step-5 is gone. IOW, adding a new path won't stick.

What am I doing wrong?

 

Sample Code C# 3.0 : Implicitly Typed Local Variables

C# 3.0 (VS2008) has added some new features, one of which I mentioned in an earlier thread (Lamba Expressions).

Another feature that they have added is “Implicitly Typed Local Variables”.
Local variable can now be assigned using the var keyword.
When assigning a variable as type “var”, the compiler infers the type of variable from the expression on the right side of the initialization statement.
Code: var myVar = 5; // this is compiled as an Int var myVar = “Whassup?”; // this is compiled as a string[/quote] Some of you may think this is just a “Variant” type and subverts the notion of strongly-typed, safe variables. It's not. The variable is still strongly-typed (as in Int myVar = 5; ), it's just that the compiler does the typing for you. It's basically a syntactical convenience.

Note, however, that it goes beyond simple variables. It can be used to assign just about anything.
Code: var myVar = new[] {1, 2, 3, 4); // compiles as Int[] var myVar = new {Name = “Kreij”, Site = “TPU”}; // compiles as an anonymous type containing two field members.[/quote] Let's say that you create a type that is enumerable (uses the IEnumerable interface) called Customers that contains several member fields. Two of which are CustomerName and CustomerLocation.
Code: var myVar = from c in Customers where c.CustomerLocation == “Chicago” select c;[/quote] The above will compile as a “IEnumerable<Customer>” type.
You can then declare another var to enumerate through the first.
Code: foreach (var record in myVar) { console.Writeln(“Customer Name = {0}”, record.CustomerName); {[/quote] This will give you all customer names in Chicago.

As you can see, this syntactical shortcut will ease the carpal tunnel of many a programer *Smile

There are a few caveats, however ...

You cannot initialize the variable to null
Code: var myVar = null; //Error[/quote] You cannot use them is class scope
Code: public class myClass { var myVar = 5; //Error public myClass () { } }[/quote] They cannot be used in the initialization expression.
Code: var myVar = myVar++; //Error[/quote] You cannot do multiple initializations.
Code: var myVar = 5, myVar2 = "Whassup?"; // Error[/quote] If you create a local variable name “var” in scope, the compiler will throw an error if you try to use the “var” keyword.
Code: Int32 var = 5; var myVar = 10; // Error[/quote] Just so you know here is the recommendation from MS on this ...

Have fun coding !!

 

c# passing variable reference.

What you need (I think) to do is move List<domain.Results> tempory = new List<domain.Results>(); outside of tcResponse (probably make it a private member of TCResponse class). If it is inside, everytime you raise tcResponse, temporary will be reinstantiated (effectively making it always contain one member).

Spoiler: Doubt it will help. You pass a variable by reference using the ref keyword in the method declaration:
Code: public void Method(ref object variable)[/quote] You'll also need to put ref in front of the variable when you send it or Visual Studio will throw a compile error.

I think what you're talking about is making a copy out of an object instead of passing a reference (C#'s default behavior). To do that, I used this deserialize function in the past and it did the trick:
Code: using System.IO; using System.Runtime.Serialization.Formatters.Binary; /// <summary> /// Performs a basic deep copy. /// /// By: The Janitor /// From: Gunnar Peipman's ASP.NET blog - .Net and Deep Copy /// </summary> public static T DeepCopy<T>(T obj) { MemoryStream ms = new MemoryStream(); BinaryFormatter bf = new BinaryFormatter(); bf.Serialize(ms, obj); ms.Seek(0, SeekOrigin.Begin); T retval = (T)bf.Deserialize(ms); ms.Close(); return retval; }[/quote]