Although its not that much sophesticated and advanced as it was on blogger,

but I can see a few more functionalities that I required in WordPress that were not present in Blogger. 

Hope you would enjoy here as well.
 I would try and keep both the blogs updated and alive. 

  

Thanks 

-- Ashutosh Vyas

Per MSDN:

Represents text that should be kept confidential. The text is encrypted for privacy when being used, and deleted from computer memory when no longer needed. This class cannot be inherited.

Storing any sensitive data like passwords etc in the standard System.String can be a potential threat to the data for the following reasons:

>> It is stored on the Managed Heap and is not pinned in the memory, so the garbage collector can move it around at will leaving several copies in memory. The code will not know that this has happened, and even if it could figure out that the string was moved, there is no way to clear out the other copies. Instead we have to wait for the CLR to allocate another object where the sensitive data is so that the memory gets erased.

>> It’s not encrypted, so anyone who can read process’s memory will be able to see the value of the string easily. Also, if the process gets swapped out to disk, the unencrypted contents of the string will be written to the swap file.

>> It’s not mutable, so whenever it is modified, there will be the old version and the new version both in memory

>> Since it’s not mutable, there’s no effective way to clear it out when you’re done using it

Hence, .NET 2.0 introduced a new class under System.Security namespace called SecureString, that can be used in place of standard Strings to store sensitive values.

Using SecureString eliminates the above mentioned issues as:

>> The SecureString is not stored in the managed heap while standard strings are and therefore it will not be replicated to multiple locations in memory.

>> SecureStrings are stored in an encrypted form. They need to be decrypted when they are used. this period of decryption can be kept as small as possible. So even if the process is swapped out to disk while the string is encrypted, the plaintext will not end up in the swap file.

>> The keys used to encrypt the string are tied to the user, logon session, and process. This means that any minidumps taken of the process will contain secure strings which are not decryptable.

>> SecureStrings are securely zeroed out when they’re disposed of. System.Strings are immutable and cannot be cleared when you’ve finished with the sensitive data

create a SecureString, you append one character at a time:

System.Security.SecureString secString = new System.Security.SecureString();
secString.AppendChar(p);
secString.AppendChar(‘a’);
secString.AppendChar(‘s’);
secString.AppendChar(‘s’);
secString.AppendChar(‘w’);
secString.AppendChar(‘d’);

When the string contains the data you want, you can make it immutable and uncopyable by calling the MakeReadOnly method:

secString.MakeReadOnly();

To read the secure value, use the SecureStringToBSTR() method as follows:

IntPtr ptr = System.Runtime.InteropServices.Marshal.SecureStringToBSTR(secString);
string sDecrypString = System.Runtime.InteropServices.Marshal.PtrToStringUni(ptr);

The garbage collector will remove SecureStrings when they’re no longer referenced, but you
can dispose of a SecureString by using the Dispose() method:

secString.Dispose();

– Ashutosh

1. Create your custom XSD:
Since I was creating intellisense for HTML, I always required the default HTML intellisense and a few of my own. So I decided to use the XSD that VS IDE uses to provide intellisense in HTML view. Those XSDs could be found located at

“%vsInstallDir%\Common7\Packages\schemas\html”

Here, since my IDE was using IE6_0.XSD, I decided to make a copy of it and make my own XSD out of it, so that I could get all the custom HTML intellisense. So I copied IE6_0.XSD and created “MyCustom.XSD”

Now to that XSD I made some changes that I required. For example, when you have a TD tag in the HTML, you do not have an attribute called TYPE. I required an attribute TYPE which could have two possible values: DATA / AGGREGATE.

So basically I required my TDs to be somewhat like :

<TD type=”Data”/> OR <TD type=”Aggregate”/>

So to attain this, following changes were made to the MyCustom.xsd

• At the location where element TD is defined, add a new Attribute Group called
  “cellTypeAttributeForHiText” (You can have any name you like).

• Next we need to create this Attribute group called “cellTypeAttributeForHiText”. For this we can define a new Attribute group as in the picture.

• While creating this Attribute group, we would be creating a simple type that would provide us the dropdown list in the intellisense when we write “Type=” in the IDE.

Apart from these, there are a couple more changes that are required so that the IDE distinguishes between the two schemas.<xsd:schema version=”1.0″ targetNamespace=’http://schemas.microsoft.com/intellisense/MyCustomSchema‘
xmlns=’http://schemas.microsoft.com/intellisense/MyCustomSchema‘
xmlns:xsd=’http://www.w3.org/2001/XMLSchema’
xmlns:vs=’http://schemas.microsoft.com/Visual-Studio-Intellisense’
vs:clientom=”ie6_0dom.tlb”
vs:ishtmlschema=”true”
vs:isserverschema=”false”
vs:htmlflavor=”4.0″
vs:MultipleScriptLanguages=”true”
vs:cssschema=”CSS 2.1“
vs:SuccinctFriendlyName=”My Custom Schema“>

SO now we are all done with the changes. We have a well made XSD to use with our IDE.

2. Make this XSD available to VS.NET IDE

In order to make this XSD available to VS IDE, we need to perform two steps.

• Firstly copy the XSD file to the location where the default XSDs for IDE are located.
• Secondly make a registry entry to register this schema with the IDE. For this, create a .reg file with the following text:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\{1B437D20-F8FE-11D2-A6AE-00104BCC7269}\Schemas\Schema 21]

“Friendly Name”=”My Custom Schema”

“URI”=“http://schemas.microsoft.com/intellisense/MyCustomSchema”

“File”=”html\\MyCustom.xsd”

Running this script would add the information to the Registry and would register the schema to the VS.NET IDE.

One thing to note here is that I have hardcoded the name SCHEMA21. This was because on my machine, I had 20 Schemas already loaded. By default, VS.NET creats 20 schemas and hense we need to maintain the order to get the schema working. Hense the number.

3. Using the custom XSD

Once we close the IDE and reopen it, now this Schema would always be available to the IDE. For using this, goto the IDE, open the HTML designer and you would see a dropdown on the toolbar of the IDE for selecting TARGET SCHEMA FOR VALIDATION

In the dropdown we will find our custom schema listed and by selecting that schema, we could now have intellisense from our own XSD file

I would thank Mikhail Arkhipov for the help he provided

In the EnvironmentEvents module, choose the event
“DocumentEvents_DocumentSaved”

This event will be called every time a document is saved in Visual Studio IDE.

Here in you could have all your validations and all those will be thrown back to IDE using your own system of exception throwing, which could possibly be via MessageBox or some message in Output Window etc.

Now in order to get the items into Output window or task list, we can use the following piece of code.

Dim projItem As EnvDTE.Solution
Dim tw As TaskList = CType(win.Object, TaskList)
win = projItem.DTE.Windows.Item(Constants.vsWindowKindTaskList)
tw = CType(win.Object, TaskList)tw.TaskItems.Add(“ErrorCategory”, Document.Name, “Error Message”, vsTaskPriority.vsTaskPriorityHigh, , True, Document.Name, -1, True, True)

– Ashutosh