在共享主机环境中为 DotNetNuke 设置 SQL 连接字符串
我正在共享托管环境中设置 DotNetNuke 应用程序,并且我对 ASP.Net 世界非常陌生。在共享环境中,我有 web.config 文件吗?或者我的主机是否必须为我设置连接字符串?
我可以通过主机的控制面板访问 IIS。
非常感谢任何帮助。
我访问了 DotNetNuke Wiki,它为我提供了有关连接字符串本身的指导,但我似乎无法找到 web.config 文件。
I'm setting up a DotNetNuke application on a shared hosting environment and I'm really new to the ASP.Net world. In a shared environment, do I have a web.config file? or does my host have to set up my connection string for me?
I have access to the IIS through my host's control panel.
Any help is greatly appreciated.
I've visited the DotNetNuke Wiki and it's given me guidance on the connection string itself, but I can't seem to locate the web.config file.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
DotNetNuke 将在安装过程中为您设置连接字符串。
当您选择“SQL Server 数据库”时,它会询问您:
在继续下一步之前,安装程序将确保它可以根据您提供的信息访问数据库。
如果成功,并且继续下一步,则意味着已经为您设置了连接字符串。
那么您从哪里获取第 1 - 4 步的信息?
sa
登录凭据 - 但最好您可以创建自己的凭据并为他们提供在此步骤中仅访问您的 DNN 数据库的权限。DotNetNuke will setup the connection string for you during the install process.
When you select "SQL Server Database", it will ask you for:
Before proceeding to the next step, the installer will make sure it can access the database given the information that you provided.
If it succeeds, and the next step proceeds, that means the connection string was already setup for you.
So where do you get your information for steps 1 - 4?
sa
login credentials for Step 4 -- but it's best if you can create your own credentials and provide them access to only your DNN database for this step.在共享主机环境中,您将拥有自己的 web.config 文件,对于大多数主机,如果没有更高级的控制面板,您至少应该能够通过 ftp 访问它。
在共享托管环境中,某些 web.config 设置将由主机指定,并在您自己的 web.config 中被忽略。例如,无论您如何配置自己的 web.config,主机都可能会强制您的站点在中等信任下运行。
In a shared host environment you will have your own web.config file, with most hosts you should be able to at least access it via ftp if not some fancier control panel.
In a shared hosting environment some web.config settings will be dictated by the host and ignored in your own web.config. For example the host will likely force your site to run under medium trust no matter how you configure your own web.config.