Search This Blog

Thursday, June 10, 2010

Security Changes in the .NET Framework 4

         There have been two major changes to security in the .NET Framework version 4. Machine-wide security policy has been eliminated, although the permissions system remains in place, and security transparency has become the default enforcement mechanism. In addition, some permission operations that presented the potential for security vulnerabilities have been made obsolete.

Code access security (CAS) has not been eliminated, Security policy has been eliminated from CAS, but evidence and permissions are still in effect. A few permissions have been eliminated, and transparency has simplified the enforcement of security.
We should be aware of the following key points:
  • Transparency separates code that runs as part of the application from code that runs as part of the infrastructure. It was introduced in .NET Framework version 2.0, and has been enhanced to become the code access security enforcement mechanism. Unlike security policy, level 2 transparency rules are enforced at run time, not at assembly load time. These rules are always in effect, even for assemblies that run as fully trusted by default. However, level 2 transparency does not affect fully trusted code that is not annotated, such as desktop applications. Assemblies (including desktop assemblies) that are marked with the SecurityTransparentAttribute and that call methods marked with the SecurityCriticalAttribute receive a MethodAccessException. You can change this behavior by applying the SecurityRulesAttribute and setting the SecurityRulesAttributeRuleSet property to Level1; however, you should do this only for backwards compatibility. You must explicitly mark a desktop application as security-transparent to apply transparency restrictions to it.
  • Code that calls security policy APIs receives a NotSupportedException in addition to compiler warnings at run time. Policy may be re-enabled by using the configuration element. When policy is enabled, security transparency is still in effect. Security policy is applied at assembly load time and has no effect on transparency, which is enforced by the runtime.
  • The obsolete request permissions (RequestMinimum, RequestOptional, and RequestRefuse) receive compiler warnings and do not work in the .NET Framework 4, but they do not cause an exception to be thrown. Deny requests cause a NotSupportedException to be thrown at run time.
  • The LinkDemand security action is not obsolete, but it should not be used for verifying permissions. Instead, use the SecurityCriticalAttribute for types and methods that require full trust, or use the Demand method for types and methods that require individual permissions.
  • If your application is built with Visual Studio 2010, you can run it without these changes by specifying a target .NET Framework version that is earlier than the .NET Framework 4 in the Visual Studio project settings. However, you will not be able to use new .NET Framework 4 types and members. You can also specify an earlier version of the .NET Framework by using the element in the startup settings schema in your application configuration file.

    For more things move to the msdn site ...

Wednesday, June 9, 2010

Currently creating a video tutorial to develop a web browser in Visual Studio 2010

Hello friends...
I am currently working on a interesting task of creating a tutorial video for developing a web browser in Visual Studio 2010.
I will upload my tutorial video in my Website and in this Web Blog, and also in You Tube...
Keep touching this blog for the video ...

Monday, June 7, 2010

Integrated Dev Environment - Visual Studio 2010 - Enhancements

Integrated Development Environment
Some of the features of the IDE Visual Studio 2010 ...

The following sections describe enhancements to the Visual Studio integrated development environment (IDE).

Navigate To

You can use the Navigate To feature to search for a symbol or file in source code. You can search for keywords that are contained in a symbol by using Camel casing and underscore characters to divide the symbol into keywords.
For more information, see How to: Search for Objects, Definitions, and References (Symbols).

Highlighting References

When you click a symbol in source code, all instances of that symbol are highlighted in the document.
For many control structures, when you click a keyword, all of the keywords in the structure are highlighted. For instance, when you click If in an If...Then...Else construction, all instances of If, Then, ElseIf, Else, and End If in the construction are highlighted.
To move to the next or previous highlighted symbol, you can use CTRL+SHIFT+DOWN ARROW or CTRL+SHIFT+UP ARROW. For more information, see How to: Use Reference Highlighting.

Generate From Usage

The Generate From Usage feature enables you to use classes and members before you define them. You can generate a stub for any class, constructor, method, property, field, or enum that you want to use but have not yet defined. You can generate new types and members without leaving your current location in code. This minimizes interruption to your workflow.
Generate From Usage supports programming styles such as test-first development. For more information, see Generate From Usage.

IntelliSense Suggestion Mode

IntelliSense now provides two alternatives for IntelliSense statement completion: completion mode and suggestion mode. Suggestion mode is used when classes and members are used before they are defined. For more information, see List Members.

Subscribe for  such posts here in this blog.. Over the bottom page

Sunday, June 6, 2010

IntelliTrace - Debug Your Application In An Efficient Manner

When you develop a project, you may be cross checking for errors, by debugging the particular project. Either fully project or, by setting few break points and you will run the program under the debugger. And if errors are found, you rectify it. Don't you think that it is the ancient method of debugging or compiling a program.

Why don't you switch to a better option like INTELLITRACE ...
In Visual Studio 2010 Ultimate, you will find this feature. This  new IntelliTrace feature brings debugging into the 21st century by giving developers better insight into their applications’ execution.
Actually Visual Studio 2010 monitors the program and collects the data about that particular application during the execution, for the convineince of the programmer in finding their errors. The collected data is referred to as IntelliTrace events. These events are collected as part of the default debugging experience, and among other things, they let developers step back in time to see what happened in an application without having to restart the debugger.

Here i have attached some of the screen shots from MSDN forum ...

And you can still learn more about this, feature , here, the MSDN forum,
and also you can also see the information about this article here,

Saturday, June 5, 2010

Choosing a .Net Framework Version

Choosing .Net Framework

           The most interesting thing about Visual Studio 2010 is that it enables us different working environments. That is if you like you can develop a project or an application that is in accordance with .Net Framework 3.5, then you can do so in this Visual Studio 2010 itself. It sounds great.

You will be noticing a drop down list in the New Project dialog box, having options such as .Net Framework 2.0, .Net Framework 3.0, .Net Framework 3.0 or .Net Framework 4.0 and ...

If your option is ,
  •    .Net Framework 2.0, then you will be using the .Net Components that are in .Net Framework 2.0 
  •    .Net Framework 3.0, then you will be using the .Net Components that are in .Net Framework 3.0
  •    .Net Framework 3.5, then you will be using the .Net Components that are in .Net Framework 3.5
  •    .Net Framework 4.0, then you will be using the .Net Components that are in .Net Framework 4.0
  •    And if you are selecting then, it will fetch you to the following link ,                             
And the web page will be ....

And here, you can surf for still more different '.Net Frameworks' and after installing them in your computer, you will be able to work under that particular framework...

Starting a Project in Visual Studio 2010

It is very simple and any one who has already worked VS 2005 or any other Visual Basics IDE can do it.
It is just by , File ----> New -----> Project
And the following dialog box appears...

  • First prefer selecting the Language that you are going to use (here as 'Installed Templates') ...
  • And then select the item or the class any component that you are going to develop.
  • Type the solution name for the application that you are going to develop in the NAME text box
  • Check for the path of your project file.
And then now you are ready to start the project.. Click 'OK'
Start you project then .... Happy Software Development........

Still in Visual Studio 2008 ... Switch to THE best IDE

         Are you still in Visual Studio 2008 ... If so then you are too late to enjoy such a world's greatest and cool invention from Microsoft® , the masters of software.
It is nothing but, my favorite Visual Studio 2010
The developer has released various trial editions of this product. Say, BETA & RC etc ...

And in the full release, they were so great to provide the Visual Studio 2010 in three different versions, which users can buy based on their requirements.

And off course they are
If you wish to try a trial before buying the product, then don't hesitate to visit and download the link at 
                                                              TEST Professional 
 And if you wish the official downloading site of Visual Studio 2010, Click Here