|
| |
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
Learn to avoid common mistakes when
developing with the ASP.NET Datagrid control.
Marcie Robillard's very useful “Common
DataGrid Mistakes” article |
|
Visual Studio Tools for the Microsoft Office
System
- Create assemblies that run in process with
Microsoft Office Excel 2003 and Microsoft Office Word 2003
- This enables you to create document-centric
solutions that utilize the power of the hosting application
Although it is possible to automate Excel or
Word from managed code, doing so requires an external application manipulating
the particular Office application from the outside. Assemblies produced with
Visual Studio Tools for the Microsoft Office System enable managed code to work
with the hosting application at a more intimate level. Although it's possible to
create a COM add-in using managed code, the new framework provided by Visual
Studio Tools for the Microsoft Office System enables you to create a solution
that is tightly integrated and, more importantly, specifically designed to use
managed code.
Detailed
article click here: |
|
I found Migration from ASP to ASP.NET is little crazy
- Statements like Dim rsInReply where rsInReply is used as RecordSet object
gets converted into 1 dimensional array ( Dim rsInReply() As Object) , but
this was no the case with all other dim statements
- on stattements like <%=rsInReply("PostedBy")%> if you get
this message in return "System.__ComObject" .you need to manually change to
rsInReply("PostedBy").Value
- Its was strange to know that ASP statement like <%=
rsMessage("PostedBy") %> get converted as <%=rsMessage(CInt("PostedBy"))%>,
now why he uses CInt, I don't know, had to manually remove CInt, but again
this was not the case with all <%=
rsMessage("PostedBy") %> statements and other such similar
statements
- Response.Write(" in reply to <B>" &
rsInReplyTo(CInt("Subject")) caused error BC30452: Operator
'&' is not defined for types 'String' and 'ADODB.Field'.
Rest everything was cool |
|
|
|
|
|
|
|
|
|