Configuration :: App Path Connection From ASP.net?
Aug 17, 2010
i have done a project using ASP.NET and SQL database...and it's working good.but everytime i run the project in other computers i need to set connection path to database.without set connection how to run the project.using "App Path"? please let me how to set App Path in ASP.NET PROJECT.
I have a custom ASP.NET application that I utilize for several clients that I host. Each client has a separate domain and the application is normally a child application under the root domain [URL]. The application files are the same (aspx, ascx, style sheets, images, etc.). The only thing different is the web.config file for each client. As development of the application continues to evolve, I have to update the application for each directory and this obviously becoming tedious. I am trying to come up with a method keep the application up to date. My first though is placing the application into a single physical path and creating multiple applications pointing to that path (the problem with this method is I can't have different web.config files). I am curious as to what solution others are using in this scenario...
When I press start on my VS2010/Silverlight/C# project, it opens a new instance of the included webserver and opens my browser window so I can test the application. Unfortunately something has happened and I am not sure what it was.. The browser window now opens the starting page with a local machine path (C:...page.aspx) rather than the normal webserver path through http (http://localhost:33592/page.aspx). It is a Silverlight Navigation project using c#/asp.net code behind.
I created a DataSet(right-click project-->add new item-->DataSet) and then a TableAdaptor to it with table from database. However, when i bring the project to others computer and run, it has error.I look into the DataSet in xml and found that the path to database is actually on the computer that created the DataSet(C:DOCUMENTS AND SETTINGSUSERDESKTOPPROJECT NAMEAPP_DATADATABASENAME.MDF) My database file is located at the App_data folder. May i know is there a way to config so that whenever i run the project on different computer, the path will auto change??
I am trying to write a page to read the Excel file provided by the user. I know I can't use the FileUpload to get the full path of the file from the client PC. This give me the problem when I write the connection string for the Excel file:
[Code]....
Without the full path, I can't replace the Data Source by a variable and I definitely can't assume all users will have their Excel files named Book1.xls located in C:Doc all the time.
I have developed on a local file system then ported over to a cheap(but reliable) asp server on the web and now my path to my access mdb is askew. I see when I upload my files, they go into a wwwroot folder which looks to me to be immediately above theroot. What syntax would I use to fix my path
I wanted to impose specific timeout interval and request length on some specific pages that uploads documents of size up to 50MB. Hence I did the following config changes after going through some sites.
I keep getting error when I run the application. I tried various other ways like giving the complete path like <sitename>/<applicationname>/<v.folder name>/<filename>.I tried this on both IIS 6.0 and IIS 7.0.
I'm trying to deploy my web project to my local IIS server (C:inetpubwwwrootlunchbox). By default the in is created inside the project directory - i.e lunchboxin. This setup, however, gives me the following error when I try to open the site:
When I move the in directory outside the project root (i.e C:inetpubwwwrootin), the site opens up just fine. I'm also able to test the web project from Visual Studio without any issues.
Can someone tell me why I have to move the in directory outside the project root to make the site work? What can I do to not have to do this?
i deployed all the pagesof mysite,but there is problem in the default page,specifically in the album images in the default page and the Error in this line
i has an page, there i have to export the file under the same virtual directory and have to save that saved location to the Database table, below is my code
my doubt is by the above code the Table-Path seems D:WinnerVirdir1Imageimg1.jpeg then next i assign the same path to the image control but the image is not displaying, incase if i hosted to any other server then also it should work.
I have an issue trying to connect to a mapped drive from an asp.net application.I tested my code on the development machine and it was successful.
[Code]....
"z" is a mapped network drive. My web servier is a virtual server Windows 2003 R2.When I try to create the dirctory on z drive I got the following error.Could not find a part of the path 'z:uploadsuser1-timenowIF I change the path from "z" to local drive like "c" it works fine.I tried to use Impersonate true to one user account ("let's call webuser which has full access to that z drive") and I still get the same error.
I am doing SOA architecture and the data base is in service side ie.within the project(website 7)
how can i can mention relative path for the data source ?
OleDbConnection aConnection = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Documents and Settings\sathiyabalu\My Documents\Visual Studio 2005\WebSites\WebSite7\App_Data\alumni_member.mdb");
i have developped an application localy that can browse excel files, pictures etc... and display them, the thing is, that on my PC when a user upload a picture it will be saved under local disk C: and to browse it i will access C:idpicture and display it, that easly. the problem is when i deployed the application on iis 7.5 it's not working anymore giving me an error saying that the path is wrong or the name of the file is changed etc...
i have understood that i can't put it on local disk C: because the picture or the excel file must be shared on all the PC's, so i have created a map network drive (PUBLIC X:) which is availble on all PC's, that way i will browse in X:idpicture but that is not working aswell.
my question is: what is the proper path to use to access file on the server (PUBLIC X: or C:) using IIS?
I have created a setup for my application which is having both website and desktop application. i m supposed to changes connection string in both the config files at runtime. i used following code :
I need to create a website using asp .net and code in vb .net.I have textbox and button in the website and a folder of data. Once user insert for example, id, it will call out the data from the folder.How should i do it? Should i used streamreader? or should i create a database, since there is no database.the file can be open using notepad.
I want to I get the file path test.config.How do find the the path to that file ?I tried something this but it appears an error:Object reference notes Set to an instance of an object.
How can i get ConnectionString In web.Config when you are in DAL(data access layer)Some said it should me in <appSetting> but i think this is not appropriate to do because web.config have dedicate tag for connection strings.i am creating a 3 tier each layers is a project in 1 solution
Project ://solution
|_View :WebApp // Dependence (BLL,ENTITY ) |_BLL : ClassLib // Dependence (DAL,ENTITY ) |_DAL : ClassLib // Dependence (ENTITY ) |_ENTITY : ClassLib //note this is not a layes just a central data object reference
I have created a website (VB) on my local host. A couple of pages on this website use gridviews or detailsviews with an AccessDataSource connection to a MS Access database. This works perfectly. But now I want to move this website to a hosting provider. And on this hosting provider my website works well but not the pages with a connection to the Access database. I searched the whole internet for a solution but I didn't found it.
Folder structure on the host:
- db > Access databases (name: testdemo.mdb) - logs -wwwroot > website (for example, the gridview is placed on index.aspx).
I think AccessDataSource didn't work, but what kind of code may I use in the index.aspx and web.config? My hosting provider said only, use a direct link to the database and not a relative, for example: E:xxx.comdb estdemo.mdb
I have created a ASP.NET 4 application in VS 2010 using Silverlight and RIA Services.
After finishing the first release on my development pc, I'm starting some deployment testing in a server in my local network.
After sucessfully published the web application using the Visual Studio FTP publishing option, I notice two strange things:
1 - On the IIS properties of the website I have uploaded my files to, you can see now a connection string, named as LocalSqlServer that points to the aspnetdb.mdf database file. I had a look in the web.config file and I could not find this connection strind defined there. So, where is it located? Where did IIs got it from?
2 - As the aspnetdb.mdf file is not deployed withtin the web application and I a musing SQL express in my testing server, where can I drop the mdf and ldf files so they can be attached when the applicaiton runs? I know I can perform an attach operation using management studio,but I'm wandering where is the DataDirectory folder ASP.NET looks for to attach it at runtime?
I have a site with 2 web servers and NLB (Windows Server 2008 and IIS 7). I'm trying to move the site to NAS storage accessed via a UNC path.
I have copied the site files to the NAS and set all permissions on the NAS. The only change I'm making in IIS is to the sites path. I can change the path back to local storage on the web server and there is no error. I switch the path to the UNC path and I get the error.
When set to the UNC path, within IIS Manager on each web server I can successfully browse to HTML files, but I get a 404 browsing to ASPX files. I've narrowed the error down to something going on when the page directive is in the aspx file. That is, when the aspx file has only html, the page will load fine. When I add the page directive to the aspx file I get the 404:
I don't see anything in the code behind that could possible cause 404, and the site files match exactly between those on the web server and those on the NAS.