DataList , é um componente ideal para exibir um conjunto de dados a partir de uma fonte de informação, de um vector, banco de dados, etc. O objetivo é claro: ser leve e usar pouco código.
Category Archives: Microsoft
ASP.Net Microsoft TutorialsDate/Time Formats
12 de Setembro de 2006 – 16:30
{0:dd.MM.yyyy} would return 04.06.2005 (date)
{0:HH:mm:ss} would return 11:21.22 (time)
pode encontrar mais documentação aqui
Windows Live OneCare
11 de Setembro de 2006 – 15:57
Nota: Para instalar é necessário alterar o “Regional Settings” para English
Aceder a items numa CheckBoxlist
11 de Setembro de 2006 – 13:04
Dim Item As ListItem
For Each Item In cbl1.Items
If Item.Selected = True Then
‘Your Code
Else
‘Your Code
End If
Next
Microsoft .NET Framework Version 1.1
16 de Agosto de 2006 – 23:22
MS Script Encoder Decoded (Obfuscating ASP Scripts)
14 de Julho de 2006 – 10:14
MS Script Encoder Decoded
Written by: Christoph Wille
Translated by: Bernhard Spuida
First published: 11/23/2001
Viewed 49462 times. Â 45 ratings, avg. grade 2.09
In the article Obfuscating ASP Scripts I demonstrated how ASP scripts can be rendered unreadable by means of the MS Script Encoder. I also said that this will only work as a defense against the average user, but not against a determined attacker who really wants to get at the source code. To emphasize this warning, today I will present a tool for inverting this code obfuscation.
Same as the author of the tool I want to say beforehand that the purpose of this tool is intended to be nothing more than a demonstration of the in the end useless encoding of the MS Script Encoder. That its intended use does not lie in cracking other's source code ought to be obvious (and that I as the author of the article am not responsible for your actions either).
Script Encoder Revisited
To start with as a warm up exercise, let's look at the Script Encoder and its use (Download). Here we have my example file to be encoded (sample.asp):
<% @Language="VBScript" %> <% Option Explicit Response.Buffer = True Dim nVar, strVar, i nVar = 10 strVar = "Hello World" For i=1 To nVar Response.Write strVar Response.Write " " Next Response.End %>
Let us assume that this is worthy enough of protection to not let anybody with physical access to the file on the Web server read it. Therefore I would encode it in this manner:
screnc /l VBScript sample.asp encoded.asp
Execution of this command returns the encoded file encoded.asp (I word wrapped the second line for reasons of legibility):
<% @Language="VBScript.Encode" %>
<%#@~^3gAAAA==@#@&r2DkKxPA6ask1kO@#@&@#@&]/wKU/RA!WW+MP{PPD;n@#@&9ks
~xjl.S,/Y.#mDSPb@#@&@#@& .mDP{P8T@#@&/ODjl.~{PJ_nV^WPqG.V9J@#@&@#@
&oGMPr'8~KKPU#mD@#@&~,In/aG /ncMkYPkODjl.@#@&P~]/wKU/RMrO+,J@!4.@*E@#@
&1n6D@#@&"+d2Kx/n Ax[@#@&CDoAAA==^#~@%>
This is sufficiently unreadable for someone who is not inclined to invest quite some time in decoding it.
Call in the Windows Script Decoder!
Did I just write something about 'investing quite some time'? Well, if that someone does know what tools are available on the Internet (and Crackers tend to have this kind of knowledge), then 'quite some time' gets reduced to 'a few seconds'. The tool I am talking about is the Windows Script Decoder. Using it is (unfortunately) just as simple as using the Script Encoder is:
scrdec13.exe encoded.asp decoded.asp
And indeed - the output is an (almost) identical Script:
<% @Language="VBScript.Encode" %> <% Option Explicit Response.Buffer = True Dim nVar, strVar, i nVar = 10 strVar = "Hello World" For i=1 To nVar Response.Write strVar Response.Write " " Next Response.End %>
By 'almost' I mean to say that we still have to manually replace VBScript.Encode by VBScript. Other than that, we now have the original source code at hand.
Conclusion
This article serves as a warning that using the Script Encoder can only be a measure protecting us from naive customers. A determined attacker will in the worst case (from his view) smile mildly at encoded files. This yet again proves the point that as far as 'security technologies' go, it always is recommended to be informed about what tools the other side has at its disposition for circumventing them.
links relacionados:
http://www.virtualconspiracy.com/index.php?page=scrdec/download
Windows Installer 3.1 Redistributable (v2)
26 de Junho de 2006 – 11:11
| Version: | 3.1.4000.2435 |
| Knowledge Base (KB) Articlesc : | KB893803 |
| Date Published: | 9/2/2005 |
| Language: | English |
| Download Size: | 2 KB – 2.5 MB* |
his download is available to customers running genuine Microsoft Windows. Please click the Continue button to begin Windows validation.
Final official version of .NET Framework 2.0 is available for download!
14 de Junho de 2006 – 12:01
Hey, I’m happy to say that the .NET Framework 2.0 is finally finished, and the official RTM build (2.0.50727.42) is available for download on the Microsoft Download Center. Check out this location for a full list of .NET Framework 2.0 products that are available. Here are some of the most commonly requested downloads:
- .NET Framework 2.0 redistributable (x86)
- .NET Framework 2.0 SDK (x86)
- .NET Framework 2.0 redistributable (x64)
- .NET Framework 2.0 SDK (x64)
- .NET Framework 2.0 redistributable (ia64)
- .NET Framework 2.0 SDK (ia64)
A couple of important notes here:
- The .NET Framework 2.0 SDK requires that you install the .NET Framework 2.0 redistributable first, so if you want the SDK make sure to download both
- The .NET Framework 2.0 redistributable is a language-neutral package. Setup UI will appear in the language of the OS you are running setup on (more setup packaging details are here if you are interested). The resources inside of the package are English only. There will be language packs available soon that contain non-English product resources.
- The .NET Framework 2.0 SDK is English only. Non-English languages will be available soon.
Published Thursday, October 27, 2005 5:49 PM by astebner
Filed Under: Visual Studio and .NET Framework
Filed Under: Visual Studio and .NET Framework
“Page cannot be found” when browsing aspx pages in Windows Server 2003 with IIS 6.0
14 de Junho de 2006 – 11:32
You may get a Page cannot be found message when you browse aspx pages in a Windows Server 2003 environment.
That is because in Windows 2003, all the webservice extensions are “Prohibited” by default to ensure security.
To resolve this, do the following steps:
1. From your Run command, type inetmgr and press enter.
2. Expand the appropriate nodes in the IIS to locate the “Webservice Extensions” Node
3. Click on the same.
4. You will find a list of “prohibited” extensions in the right.
5. Click on ASP.NET and “allow” it
That should resolve this issue.
This article applies for Windows Server 2003, IIS 6.0 environment.
Server.Transfer Vs. Response.Redirect
12 de Maio de 2006 – 15:53
If you read a lot of industry magazines and ASP.NET code samples, you may find that, although the majority use Response.Redirect to send the user to another page, some seem to prefer the rather mysterious-sounding Server.Transfer. So, what’s the difference?
Well, Response.Redirect simply sends a message down to the browser, telling it to move to another page. So, you may run code like:
Response.Redirect("WebForm2.aspx")
or
Response.Redirect("http://www.karlmoore.com/")
to send the user to another page.
Server.Transfer is similar in that it sends the user to another page with a statement such as Server.Transfer(“WebForm2.aspx”). However, the statement has a number of distinct advantages and disadvantages.
Firstly, transferring to another page using Server.Transfer conserves server resources. Instead of telling the browser to redirect, it simply changes the “focus” on the Web server and transfers the request. This means you don’t get quite as many HTTP requests coming through, which therefore eases the pressure on your Web server and makes your applications run faster.
But watch out: because the “transfer” process can work on only those sites running on the server, you can’t use Server.Transfer to send the user to an external site. Only Response.Redirect can do that.
Secondly, Server.Transfer maintains the original URL in the browser. This can really help streamline data entry techniques, although it may make for confusion when debugging.
That’s not all: The Server.Transfer method also has a second parameter—”preserveForm”. If you set this to True, using a statement such as Server.Transfer(“WebForm2.aspx”, True), the existing query string and any form variables will still be available to the page you are transferring to.
For example, if your WebForm1.aspx has a TextBox control called TextBox1 and you transferred to WebForm2.aspx with the preserveForm parameter set to True, you’d be able to retrieve the value of the original page TextBox control by referencing Request.Form(“TextBox1”).
This technique is great for wizard-style input forms split over multiple pages. But there’s another thing you’ll want to watch out for when using the preserveForm parameter. ASP.NET has a bug whereby, in certain situations, an error will occur when attempting to transfer the form and query string values. You’ll find this documented at http://support.microsoft.com/default.aspx?id=kb;en-us;Q316920.
The unofficial solution is to set the enableViewStateMac property to True on the page you’ll be transferring to, then set it back to False. This records that you want a definitive False value for this property and resolves the bug.
So, in brief: Response.Redirect simply tells the browser to visit another page. Server.Transfer helps reduce server requests, keeps the URL the same and, with a little bug-bashing, allows you to transfer the query string and form variables.
Top Tip: Don’t confuse Server.Transfer with Server.Execute, which executes the page and returns the results. It was useful in the past, but, with ASP.NET, it’s been replaced with fresher methods of development. Ignore it.
Home