Request for the permission of type System.Net.WebPermission

your spent too much time on tring tounderstand why your application dons'nt work?? yea tell me about it, security request ...
i'm looking for it two weeks ago.. no one has no idea! until i foud this blog... http://blogs.conchango.com/kenibarwick/archive/2004/11/05/195.aspx
he said it simple! don't put your aplication on shared folder....
i stored my application on a mapped drive on my network!!
so if you did like me just copy the folder to your C drive and it's work properly!
http://www.byramix.com

Active Server Pages error ''ASP 0131'' , Disallowed Parent Path , indicate the parent directory

have got a technical problem. Can you explain me the followingstatement, please:
Active Server Pages error ''ASP 0131''
Disallowed Parent Path
/knowledgebase/admin/index.asp, line 1
The Include file ''../ScriptLibrary/incPureUpload.asp'' cannot contain ''..''
toindicate the parent directory.
answer: The problem you described is related to configuration of your web server. In order to avoid this problem please do the following
1. Go to your IIS Manager
2. Right click your web site
3. Choose Properties >
4. Select Home Directory Tab
5. Click ‘Configuration’ button
6. Select App Options Tab
7. Check the Enable Parent Paths
8. Click OK and your new configuration will be saved.
This problem occures specially on new Windows 2003 Server systems as the default setting is not to use parent paths.
Note: Another simple solution is to put your upload script page in your site root. This way it won't need to use parent paths to the ScriptLibrary folder.

SQL Server 2005 SQLExpress error: ...provider: Named Pipes Provider, error 40 - Could not open connection to SQL Server

I got this error immediately after installing VS2005 & SQL Server 2005 Express and trying to establish my first connection using the new server - not a good start at all - and by the looks of it, it's happened to many hundreds, if not thousands, of others too.Generally this error occurs if you cannot connect to the SQL server - as the message says (no sh*t). However, what's not obvious is why...First suggestion is to make sure that you specifiy the instance name as well as the server name (christ knows why, but when MS refer to "Server Name" they really mean "Server Instance Name") eg if your server was named 'bigturnip' then you need to specify 'bigturnip\sqlexpress' (where sqlexpress is the instance name - this one just happens to be the default used by SQL Server 2005 SQLExpress).If that doesn't help, then go into the SQL Server Configuration Manager and make sure you've enabled Named Pipes & TCP (if you're using it) and also go into the Surface Area Configuration tool and make sure you've set it for local &/or remote connection for the connection types you want to use. Then restart the SQL Server (instance) service.
source: http://geekswithblogs.net/timh/archive/2006/01/30/67586.aspx

How to configure SQL Server 2005 to allow remote connections

Enable remote connections for SQL Server 2005 Express or SQL Server 2005 Developer EditionYou must enable remote connections for each instance of SQL Server 2005 that you want to connect to from a remote computer. To do this, follow these steps:
1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
3. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply. Note Click OK when you receive the following message:Changes to Connection Settings will not take effect until you restart the Database Engine service.
4. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service.

Discuss Post

this is my first message

well, this is my first message in my technical blog...
check my webpage http://www.byramix.com