I am creating a Asp.Net Web APP, and I'm trying to figure out how I can allow users to create content and save it on a large file system in my Computer
My thought process being something like this:
User john113 creates a project: projectA
If the directory on the remote machine /serverstore/john113 does not exist, create it.
If the directory on the remote machine /serverstore/john113/projectA does not exist, create it.
john113 creates itemA in projectA and saves the item, I write the file to /serverstore/john113/projectA/itemA
How can I access this remote server , which is a windows machine, and be able to do the actions I've listed above.
Will I need some instance of Windows Server running on this remote machine, with open file permissions?
Related
I am making a web application in asp.net there i am making a directory in F drive through c# code. The code runs fine on my system and in IIS also but the problem is that when my partner using the same ip of my system the directory is not being created in his system i want who ever using the ip of my system the folder should be created and files should be save on that.In the second image my partner is running the application the files get save on my directory not on his system
check your local directory it will be save there not on the system using this ip address.
I have multiple applications on a IIS server. How can I set one particular application to run as user 'appuser' and all uploaded files to be saved by as this user. ASP.NET
Every single IIS application run under some so-called application pool. The application pools have default identity (App Pool Identity in newer IIS, NETWORK SERVICE in older IIS). You can also set application pool to have custom identity by specifying user credentials.
However it seems like an overkill to run application under specific user if the only thing you require is to set specific owner for files being created - so I'd rather just force file owner after the file was created instead of changing application pool identity.
See Getting / setting file owner in C#
how to do that.
UPDATE
If you have to write to folder which is restricted to (yourspecialusername) I recommend this approach:
1) Dump file to temp files folder
2) Copy your file to shared folder under the (yourspecialusername) - see - Start a .Net Process as a Different User
3) Wait for Process in 2) to exit and delete temp file
To migrate a project from one environment to another in PeopleSoft using Application Designer Connect Id credentials(default is people/peop1e) must be same in both environment.
Is there any way we can migrate projects if connect id and password are different in both the environment.
You could copy the project to a file between environments:
Save the project to a file from the source environment
Change the connect information in Configuration Manager
Copy the project from a file in the destination environment
Or it looks like you could you use App Designer Command Line parameters to copy the project from one database to another with different connect passwords but I haven't tried it. Here is the PeopleBooks page for Understanding PeopleSoft Application Designer Command Line Parameters and the Command Line Parameter Reference
My requirement is to deploy an ASP.NET application in which I have a core library class project, service layer and a UI layer, using SQL Server database as backend.
My client needs to deploy it using some MSI or EXE, in which he / she should able to customize the installation to IIS and his SQL Server.
What I want to say, when I execute the EXE, it will ask me the basic requirement for the IIS like server name, virtual directory name, app pool etc , then automatically deploy it there. Now it should also ask the same for SQL Server database installation like server name, authentication, database name and so on....
I have tried but I can manage to deploy ASP.NET app not able to customize the SQL Server installation.
Also tell a feasible solution, as my database size is around 6GB. What will be optimized way to create a installer for that?
I once had to do something similar but my database was much smaller.
I scripted out my database into T-SQL statements for its creation from scratch and stored those in a text file.
I then wrote a .NET windows app that would prompt the user for SQL Server network location and credential information. This .NET application had the database creation SQL text file included in the executable as a resource file, and would connect to the specified SQL Server and execute the commands in the text file one by one. I was able to read the text file and parse commands out by delimiting on the keyword "GO"(linebreak).
I have a web application running on IIS. Instead of using a database it reads and writes to a couple of XML files. I currently store these files in the Application Data folder in windows. This folder (\Documents and Settings\All Users\Application Data in win 2003) however requires at least "Power Users" privileges to write!
Reads are OK and are granted to everyone but writes are not allowed as long as your not in the one of the more privileges groups on the system. Why is this so? Is there a better place for a application to write to and one that does require me to add the user of the application pool to a more privileged group?
My second question is that if I have file that just needs reading. Can I then read this directly for the folder where I have my web application deployed (say a folder in "Program Files") or should I at all times use the Application Data folder?
The idea here is that this files sometimes need manual change and using the folder where the web application runs from would basically make more since to normal users I think (especially on win 2008 where the Application Data is hard to find).
Reads are OK and are granted to everyone but writes are not allowed as long as your not in the one of the more privileges groups on the system. Why is this so?
You don't want to allow just anyone to write to the file system via a web application.
Using ASP .NET, people usually use the APP_Data folder to store data files that need read/write access to an account such as Network Service.