.NET ShortCut

I need this feature in VB
,Pleeeeeeeaaaaaaaaassssssseeeeeeeeeeeeeeeeeeeeeeeeeeee
Only C# has this feature nowwwwwwwww :(

You can do this in C# :
Csc /r:ver1=assembly1.dll /r:ver2=c:\assembly1.dll myapp.cs

Here is a sample of myapp.cs file
extern alias ver1;
extern alias ver2;

using System;

class MyApp
{
static void Main(string[] args)
{
Console.WriteLine(ver1::MyLibrary.Class1.Test());

Console.WriteLine(ver2::MyLibrary.Class1.Test());
}
}

# posted by test2512 @ 5:56 PM 0 comments

This is a very interesting funny notice :
Connection Strings must be IDENTICAL . so what is new ?

Conn1 : "Server=SQL01;Database=AdventureWorks;Integrated
Security=SSPI;Pooling=true"
Conn2 : "Server=SQL01;Database=AdventureWorks;Integrated Security=SSPI
;Pooling=true"

These are not identical since the second connection string has a SPACE after
the word SSPI, so they generate two different pools.you can examine that by
SQL Profiler .
It is very interesting ha .

# posted by test2512 @ 3:18 PM 0 comments

If we have a connection like this :

Conn1 : "Server=SQL01;Database=AdventureWorks;Integrated
Security=SSPI;Pooling=true;Min Pool Size=100"

Are the 100 connections created in series(one after the other) or
parallel(all nearly at the same time) ?
To avoid Flooding the Database with Connections they are created in series .
You can check that by executing the above connection and notice the
"starttime" column in Profiler , you will notice in the profiler that they
are opened serially after each other by fractions of seconds.

# posted by test2512 @ 2:58 PM 0 comments

Why don't the logon screen just appears directly without having to press
this combination ?
As Keith Brown says in his book "A .NET Developer's Guide to Windows
Security" . Always Asking the user for his password trains the user to
always type his password whenever asked. And since it can be any
malicious code asking the user for his password so logon screens must be
kept to minimal.
The Sequence of CTRL+ALT+DELETE can only be traced by Kernel mode , so
this is a clear message from the user to the OS that "I need to type my
password to logon". This Sequence cannot be tracked by user mode. So try
seriously to use the logon user account instead of asking him.

# posted by test2512 @ 3:52 AM 0 comments

Unfortunately I still see some developers and architects see that VB is
untrustable and you still cant do a lot of things using VB, I would say to
those people "please read the Developer Division Manager Somasegar's blog
entry" http://blogs.msdn.com/somasegar/archive/2004/08/01/204540.aspx

And you can read also the Man behind VB's Blog entry :
http://www.panopticoncentral.net/archive/2004/05/31/1100.aspx

I hope you completely change your mind now specially when you know that a
lot of .NET 2.0 classes have been written entirely with VB as well as the VB
engine itself and parts of the VS IDE.

The comparison between C# and VB.NET now becomes like "which of my 2 eyes I
like better " as SomaSegar has said .i really like this phrase

# posted by test2512 @ 3:54 PM 0 comments

1. Impersonation is done on a thread basis not on a process level. So when we say that something is impersonating a user, then this something must be for sure a Thread not a process.
   
2. A thread impersonating a specific user means that the thread will be working with the security context of that user.
   
3. New created processes inherits their parents’ tokens
   
4. When a thread needs to stop impersonation for a while for example in ASP.NET if we used impersonation in web.config and a certain page needs to do a task with a specific privilege regardless the impersonated account then in that case we have to stop impersonation temporarily . there is a specific function to call in this case called “RevertToSelf”
   We can do this in .NET by :
   
   Console.WriteLine(WindowsIdentity.GetCurrent().Name); //print the impersonated account name
   
   //RevertToSelf
   //This line will remove the token impersonated and will revert back to the process identity.
   WindowsImpersonationContext c = WindowsIdentity.Impersonate(System.IntPtr.Zero);
   
   Console.WriteLine(WindowsIdentity.GetCurrent().Name); //print the process identity account name
   
   //go back to Imopersonation
   c.Undo(); // will get the impersonated token back
   Console.WriteLine(WindowsIdentity.GetCurrent().Name); //print the impersonated account name
   
5. Flow of tokens to new threads is different in .NET 1.1 than 2.0
   in the image above you can see...
   
   Step1
   A process running under Administrator Token. And a thread that is running under the same account
   
   Step2
   The thread impersonates HusseinA.
   
   Step3
   The current thread in the process spawns a new thread
   
   If thread1 spawned a new thread, what will be the token flown from thread1 to the spawned thread.
   
   In .NET v1.1 it is the original Process token which is Administrator in this case.
   Example: if a process running under “local system” and a thread in this process impersonated another lower privilege account then the current thread decided to spawn another thread. the new thread will run under local system not under the impersonated account. This is very dangerous and can lead to some flaws.
   
   In .NET 2.0 the default now is to flow the impersonated account and not the original process account.
   
   using System;
   using System.Text;
   using System.Runtime.InteropServices;
   using System.Security;
   using System.Security.Principal;
   using System.Threading;
   
   namespace ImpersonateTest
   {
   class Program
   {
   
   
   
   [DllImport("advapi32.dll", SetLastError = true)]
   static extern bool LogonUser(string lpszUsername, string lpszDomain, string lpszPassword,
   int dwLogonType, int dwLogonProvider, ref IntPtr phToken);
   
   
   static void Main(string[] args)
   {
   //get a token for a user
   IntPtr token = IntPtr.Zero;;
   bool loggedin = LogonUser("user1", "MyMachine", "P@ssw0rd", 3, 0, ref token);
   //prints the name of the process identity name Console.WriteLine(WindowsIdentity.GetCurrent().Name);
   
   //Impersonate
   WindowsIdentity w = new WindowsIdentity(token);
   WindowsImpersonationContext oldWindowsIdentity = w.Impersonate();
   
   //prints the name of the Impersonated account name Console.WriteLine(WindowsIdentity.GetCurrent().Name);
   
   
   Thread t1 = new Thread(new ThreadStart(Test));
   t1.Start();
   }
   static void Test()
   {
   //in .NET 1.1 prints the name of the Process account name
   //in .NET 2.0 prints the name of the Impersonated account name
   Console.WriteLine(WindowsIdentity.GetCurrent().name);
   }
   }
   }

# posted by test2512 @ 1:54 AM 161 comments

The motivation for building a new Application Project Model :
http://weblogs.asp.net/scottgu/archive/2005/12/07/432630.aspx

A very useful comparison between the two models :
http://msdn.microsoft.com/vstudio/default.aspx?pull=/library/en-us/dnvs05/html/WAP.asp

Very useful Tutorials :
http://webproject.scottgu.com/CSharp/Default.aspx

# posted by test2512 @ 10:48 AM 0 comments