Narendra Tiwari

http://social.msdn.microsoft.com/forums/en-US/windowsworkflowfoundation/thread/69c4b453-d331-491e-aab9-b7c1c8dae899/

• http://weblogs.asp.net/scottgu/archive/2008/11/24/new-asp-net-charting-control-lt-asp-chart-runat-quot-server-quot-gt.aspx
  
• Download Microsoft .NET Framework 3.5 SP1 Standalone Full Redistributable Setup Installer

If you want to sign an assembly, you must have the source code, then you can sign it by creating .Net Module.

1. Create .NetModule
    CSC /out:<OutputModule.netmodule> /t:module <CodeFile.cs>

2. Create a Keypair
    SN -k <KeyPairFile.snk>

3. Link Keypair with the assembly using Assembly Linker 
    AL /out:<OutputAssembly.dll> <Module.netModule> /keyfile:<Keyfile.snk>

We have a table with ntext type of field in sql server database, that actually contains text data.
ntext is used to store the unicode type of data that that takes 2 times storage size in bytes,  is two times the number of characters entered.

Now the scenario is we would like to replace all occurances of a paricular string from the data with another string.

It is very simple to do with Replace command in Sql Server, but the constraint is it only takes varchar/nvarchar type of parameter i.e. we can not run Replace command over ntext, we need to cast/convert ntext into varchar/nvarchar but in that case there are chances of loss of data it can truncate the data while convering ntext into varchar/nvarchar.

UPDATETEXT is the suitable command to achieve this for ntext, it also include other binary type of data type image and text.

Following link is demonstration of UDDATETEXT for ntext datatype:
http://sqlserver2000.databases.aspfaq.com/how-do-i-handle-replace-within-an-ntext-column-in-sql-server.html

Above scenario is for SQL Server 2k only. If we have Sql Server 2k5, we should use varchar(max) and nvarchar(max) for text and ntext.
http://sqltips.wordpress.com/2007/05/28/use-varcharmaxnvarcharmax-instead-of-text-ntext/

1. Create 2 shared assemblies with different versions (1.0.0.0 and 2.0.0.0).

2. For assembly 1 include the following reference in project file.
    <Reference Include="TestAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=508b5c5f7455410a, processorArchitecture=MSIL">
      <HintPath>..\..\TestAssembly\T1\TestAssembly.dll</HintPath>
      <Aliases>Test1</Aliases>
      <Private>False</Private>
    </Reference>

Hint Path Vs Reference Path
As for the "Referece Path" or "Hint Path" in the VS.NET project's setting
files, they're all design-time /dev-time setting used by the IDE. As
described in the IDE's help doc, "Reference Path" are used by the VS.NET
IDE to load all the assembliy references when the Project is loaded into
the VS.NET IDE. And the "Hit Path" is mainly used for building time, when
the IDE will build the project, it'll locate the assemblies which is
required to link through the "Hint Path". Anyway, they're all internally
used by the VS.NET IDE, and is possibly to change in sequential version and
they have nothing to do with the .NET framework CLR's runtime assembly
locating.

For .net framework CLR's runtime assembly locating, it'll follow a well
defined steps, generally, it'll check GAC (if strong-named) first, then,
codebase settting , and private path probing. Here is a MSDN reference
which describing the .NET framework's runtime assembly locating.

3. Form assembly 2 include the following reference in the project file.
    <Reference Include="TestAssembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=275b13b4e9b16f25, processorArchitecture=MSIL">
      <HintPath>..\..\TestAssembly\T2\TestAssembly.dll</HintPath>
      <Aliases>Test2</Aliases>
      <Private>False</Private>
    </Reference>

4. While refering the above assemblies set extern aliases for both the assemblies
      extern alias Test1;
      extern alias Test2;

5. And then we can use Test1 and Test2 as 2 different namespaces

      Test1.TestAssembly.TestClass t1 = new Test1.TestAssembly.TestClass();
      MessageBox.Show(t1.Add(2, 3).ToString());

      Test2.TestAssembly.TestClass t2 = new Test2.TestAssembly.TestClass();
      MessageBox.Show(t2.Add(2, 3, 4).ToString());

Please note the project referencing both the assemblies will be compiled with the following warnings.

CAMSTUDIO A cool tool that lets you record a video of a section of your screen.  It saves to AVI format, though it also has a feature to convert to a SWF to embed it in a web page.  It’s opensource too. :)

 http://camstudio.org/

• Docx to Doc conversion
  • http://fmshaon.blogspot.com/2007/07/how-to-convert-docx-to-doc-without.html

• Download Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
  • http://fmshaon.blogspot.com/2007/07/how-to-convert-docx-to-doc-without.html

We need to update the SSL certificate to get it work, we can also ignore the above error just by adding following highlightrd lines in the code, in that case communication will no longer be secure.

Const SXH_SERVER_CERT_IGNORE_ALL_SERVER_ERRORS = 13056
set objHttp = Server.CreateObject("MSXML2.ServerXMLHTTP.3.0")
objHttp.setOption(2) = SXH_SERVER_CERT_IGNORE_ALL_SERVER_ERRORS
objHttp.Open "POST", "https://<POSTURL>", false
objHttp.send objRequest

Ravi launched the .Net Video site:- http://www.dotnetvideos.net/

The PUT method not as widely used as the POST method is the more efficient way of uploading files to a server. This is because in a POST upload the files need to be combined together into a multipart message and this message has to be decoded at the server. In contrast, the PUT method allows you to simply write the contents of the file to the socket connection that is established with the server.

When using the POST method, all the files are combined together into a single multipart/form-data type object. This MIME message when transferred to the server, has to be decoded by the server side handler. The decoding process may consume significant amounts of memory and CPU cycles for very large files.
The disadvantage with the PUT method is that if you are on a shared hosting enviorenment it may not be available to you. we need to enable the PUT verb for the server extension

Enable PUT on IIS web server:-
=========================
1. Select Virtual Directory  2.=> Properties 3.=> Configuration 4.=> Under Mappigs Tab - select extension (e.g. .aspx)=> add PUT in verb list.

The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request identifies the entity enclosed with the request.

Sample Code:-   Following code sample will be used to test the PUT method for Uploading the file, here ASP and VBScript is used in the sample, I'm using XmlHttpRequest object for making HttpRequest and getting the HttpResponse back from the web server.
refernces:- http://upload.thinfile.com/docs/put.php