-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard Birkby
Sent: Thursday, 9 January 2003 2:30 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Does CLR support SSE or SSE2?
John St. Clair wrote:
In your
DA I am using VS.NET 2002 with SP1. I know there was some kind of problem
DA with the first VS release but SP1 fixed that. This particular problem
DA really is maddening. Makes debugging a little difficult when you can't set
DA a breakpoint where you want it.
SP1? Could you tell me where I
You can add a CompilerOptions attribute to the Page directive like this:
%@ Page CompilerOptions=/unsafe Language=C# %
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]]On Behalf Of Dominick Baier
Sent: Thursday, January 09, 2003 3:39 AM
Somehow related to this, here is an interesting article:
http://cedar.intel.com/cgi-bin/ids.dll/content/content.jsp?cntKey=Generic+Editorial::dotnet_boost_perform_frameworkcntType=IDS_EDITORIALcatCode=BZK
Christian Weyer
[MVP ASP.NET XML Web Services | AspElite Member]
**
Hello,
I have a small problem to solve to the best possible solution, and I am
starting to feel that there might not be one. Maybe some of you can
comment.
Basically, I write a generic db abstraction layer (the generic is
important here). I need to keep fine grained control over mydb locks -
Gosh, that's being a bit harsh. He already admitted that it's not as secure
as a random salt. While it's true that using a derived salt is not as secure
as a random salt, it is definitely more secure than using no salt at all.
With this approach, it is required that A) the black hat know your salt
Hi,
i try to put some unsafe code directly in an .aspx file (no code behind)
on execution i get the the error that i should compile with the /unsafe
switch. but i don't have a (il) compilation.
msdn talks about a attribute AllowUnsafeBlocks witch sets the /unsafe switch
programmatically. but
