D
DKode
remove the <connectionstring /> from your web.config file?
D
dirk
Hello,
Im am trying to create - for the very first time - an asp page
(default.aspx) with visual web developer 2005 express Edition.
I have put a simple button in my default.aspx page with very little code
behind this button.
this is the content of my default.aspx.vb page :
Partial Class _Default
Inherits System.Web.UI.Page
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Button1.Click
MsgBox("hallo")
End Sub
End Class
-------------------------------------------------------------------------------------------------------------------------------------------------------
this is the content of my web.config file :
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="false" strict="false" explicit="true" />
<pages>
<namespaces>
<clear />
<add namespace="System" />
<add namespace="System.Collections" />
<add namespace="System.Collections.Specialized" />
<add namespace="System.Configuration" />
<add namespace="System.Text" />
<add namespace="System.Text.RegularExpressions" />
<add namespace="System.Web" />
<add namespace="System.Web.Caching" />
<add namespace="System.Web.SessionState" />
<add namespace="System.Web.Security" />
<add namespace="System.Web.Profile" />
<add namespace="System.Web.UI" />
<add namespace="System.Web.UI.WebControls" />
<add namespace="System.Web.UI.WebControls.WebParts" />
<add namespace="System.Web.UI.HtmlControls" />
</namespaces>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows" />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly"
defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
</configuration>
------------------------------------------------------------------------------------------------
when uploading these files to my provider and testing my page, i always get
an error in the web.config file saying that the <connectionStrings/> is not
ok.
I contacted my proveder, but they do not support scripts, they just say that
my web.config file isn't ok.....
Can somebody please help me with a web.config file that will work?
I do also have problems configuring my IIS. Do i have to make a virtual
directory to make my test work? Or is IIs just made to test localy?
thank you.
Im am trying to create - for the very first time - an asp page
(default.aspx) with visual web developer 2005 express Edition.
I have put a simple button in my default.aspx page with very little code
behind this button.
this is the content of my default.aspx.vb page :
Partial Class _Default
Inherits System.Web.UI.Page
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Button1.Click
MsgBox("hallo")
End Sub
End Class
-------------------------------------------------------------------------------------------------------------------------------------------------------
this is the content of my web.config file :
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="false" strict="false" explicit="true" />
<pages>
<namespaces>
<clear />
<add namespace="System" />
<add namespace="System.Collections" />
<add namespace="System.Collections.Specialized" />
<add namespace="System.Configuration" />
<add namespace="System.Text" />
<add namespace="System.Text.RegularExpressions" />
<add namespace="System.Web" />
<add namespace="System.Web.Caching" />
<add namespace="System.Web.SessionState" />
<add namespace="System.Web.Security" />
<add namespace="System.Web.Profile" />
<add namespace="System.Web.UI" />
<add namespace="System.Web.UI.WebControls" />
<add namespace="System.Web.UI.WebControls.WebParts" />
<add namespace="System.Web.UI.HtmlControls" />
</namespaces>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows" />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly"
defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
</configuration>
------------------------------------------------------------------------------------------------
when uploading these files to my provider and testing my page, i always get
an error in the web.config file saying that the <connectionStrings/> is not
ok.
I contacted my proveder, but they do not support scripts, they just say that
my web.config file isn't ok.....
Can somebody please help me with a web.config file that will work?
I do also have problems configuring my IIS. Do i have to make a virtual
directory to make my test work? Or is IIs just made to test localy?
thank you.
D
dirk
I have already done this, but then i get other messages
namespaces not ok, when i remove this,
i get an error in _default
and so on...
namespaces not ok, when i remove this,
i get an error in _default
and so on...
G
Guest
One thing to consider is where and to whom do you suppose that MsgBox will
display? Try this:
Create a new website
Add a button (Button1) to default.aspx
Add a label (Label1) to default.aspx
Double click the button and add the single line of code:
Label1.Text = "my Message"
Run the project.
You should initially just see the button until you click it at which point
the label will have "my Message" in it.
Hope this helps, the begining is the worst
display? Try this:
Create a new website
Add a button (Button1) to default.aspx
Add a label (Label1) to default.aspx
Double click the button and add the single line of code:
Label1.Text = "my Message"
Run the project.
You should initially just see the button until you click it at which point
the label will have "my Message" in it.
Hope this helps, the begining is the worst
S
Shimon Sim
Does your provider support ASP.NET 2.0?
A lot of them don't.
A lot of them don't.
D
dirk
Yes,
they support it
they support it
Shimon Sim said:
D
dirk
So when i remove <connectionString/> from my web.config, i get the following
error when i ask my page on www.pauldesmedt.be/asp/default.aspx
Or maybe, im a doing something wrong not using IIS for this project?
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Child nodes are not allowed.
Source Error:
Line 24: <compilation debug="false" strict="false" explicit="true"
/>
Line 25: <pages>
Line 26: <namespaces>
Line 27: <clear />
Line 28: <add namespace="System" />
Source File: C:\Program
Files\Sphera\ServerDirector\accounts\pauldesmedt.be\www\asp\web.config
Line: 26
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300
error when i ask my page on www.pauldesmedt.be/asp/default.aspx
Or maybe, im a doing something wrong not using IIS for this project?
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Child nodes are not allowed.
Source Error:
Line 24: <compilation debug="false" strict="false" explicit="true"
/>
Line 25: <pages>
Line 26: <namespaces>
Line 27: <clear />
Line 28: <add namespace="System" />
Source File: C:\Program
Files\Sphera\ServerDirector\accounts\pauldesmedt.be\www\asp\web.config
Line: 26
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300
Ravi Ambros Wallau said:
R
Ravi Ambros Wallau
First of all, remove <connectionString/>.
A connection string (and other parameters) can be put on web.config using
the <appSettings> session, like this:
<configuration>
<appSettings file="Rainbow.config">
<add key="SomeKey" value="SomeValue" />
</appSettings>
To access these values, use the
System.Configuration.ConfigurationSettings.AppSettings["SomeKey"] statement.
Other thing:
MsgBox can't be used on WebPages... It's intended to be used only with
WinForms...
You'll probally receive a compilation error message when you try to open
this page (but that, only web.config is correct)...
A connection string (and other parameters) can be put on web.config using
the <appSettings> session, like this:
<configuration>
<appSettings file="Rainbow.config">
<add key="SomeKey" value="SomeValue" />
</appSettings>
To access these values, use the
System.Configuration.ConfigurationSettings.AppSettings["SomeKey"] statement.
Other thing:
MsgBox can't be used on WebPages... It's intended to be used only with
WinForms...
You'll probally receive a compilation error message when you try to open
this page (but that, only web.config is correct)...
S
sloan
I had to explictly tell my hosting company to "Move Application1 to 2.0".
Locally, under IIS, there is a tab which says "run this at 1.1 or 2.0".
With the hosting company, I can't run IIS, thus they had to do it for me.
as far as:
MsgBox("hallo")
You're not in the winforms world anymore. That code doesn't make sense.
As previously stated, draw a textbox on your form.
Do something like this:
TextBox1.Text = "hello"
or
TextBox1.Text = DateTime.Now.ToLongTimeString()
...
Locally, under IIS, there is a tab which says "run this at 1.1 or 2.0".
With the hosting company, I can't run IIS, thus they had to do it for me.
as far as:
MsgBox("hallo")
You're not in the winforms world anymore. That code doesn't make sense.
As previously stated, draw a textbox on your form.
Do something like this:
TextBox1.Text = "hello"
or
TextBox1.Text = DateTime.Now.ToLongTimeString()
...
M
Mark Fitzpatrick
I would guess that they support ASP.Net 2.0, but your account is runing
against ASP.Net 1.1. The connectionstring error is a good indicator since it
was added in 2.0 and this is exactly the kind of error you expect to see
when it is thrown onto a server using the 1.1 framework.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
against ASP.Net 1.1. The connectionstring error is a good indicator since it
was added in 2.0 and this is exactly the kind of error you expect to see
when it is thrown onto a server using the 1.1 framework.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
M
Mark
"ConfigurationStettings" is deprecated. Use "ConfigurationManager" for
2.0.
Mark
2.0.
Mark