I'm building a site that can possibly have millions of users (yes ambitious!). Each user can upload an image or two for his/her profile. How would you architect the directories to support this type of thing? I was thinking of having a users subfolder off the root dir where each user will have their own sub-dir that corresponds to their userId created at registration time. I could then upload their profile pics to their corresponding sub-directory under the users dir. Seems straightforward but am I missing anything? Can I have a million sub-dirs under the user dir? NTFS supports it so my guess is YES.
I want to allow each user to create a webpage on our domain. example: www.site.com/username
I've created a few pages that get content from database and place it in a folder. I want each user to be able to edit their own data and when they hit "submit". the system will then copy those pages to a folder and modify the code so it read from the right database.
I keep getting "virtual directory not being configured as an application in IIS" errors. Is there any way around this error? I want the process to be 100% automatic so that I don't need to manually go into the server and configure the IIS myself.
I have a large directory structure with JavaScript, images, etc. that depend on each other. I would like to encapsulate it all into a DLL so I only have to reference one thing and not have multiple copies of all these files across projects.
Because the files depend on each other, I'm thinking I can create an IHttpModule that registers a route to accept URLs such as /MyEmbeddedDir/subdir/file.js. Anything in MyEmbeddedDir would then be handled by a custom IHttpHandler that does the correct mapping. Each web application would then need to reference the DLL and add the module and handler to web.config. Does this seem reasonable?Also, is there an easier way to embed/reference the files than to set the build action to embedded resource and add [assembly: WebResource(...)] to each file (there are dozens!)?Edit: If I'm not using WebResource.axd then I shouldn't need to add [assembly: WebResource(...)]
I am using asp.net 3.5 and I am trying to create a project structure (asp.net web solution with UI/Business/Data access) which would be like a base and ready for any new projects in my team and all could use this standard structure only as a base(outer boundary) and they can expand the structure. Also adding on to it I wanted to include certain features like adding libraries of reusable code/functions, so that every team member could use functions from my library within this base structure. To summarize the above, I need to create standard .net project structure/framework/architecture with resusable code library included in it. How can I do this..
I am working on an ASP.NET application which has one data entry form. this form contains one field which takes Path for existing webforms.Suppose i have a form name "XYZ.ASPX" inside my working directory eg. "WEBPAGESXYZ.ASPX"Now my requirement is "Can i have a browsing control which will restrict me to browse pages and user controls in my wrking directory only and not the whole computer"
I am not new to ASP.Net application development but I haven't used some of the new frameworks or features that are used in applications these days.
For cross-cutting concerns, things like: Logging, Caching and DAAB are used in projects these days to implement proven and efficient source code from either Microsoft or other third party vendors such as Log4Net for logging purposes.
how a large ASP.NET webapplication can be structured / designed with "subwebs" !? In other words I want to structure a large web-application where I have a solution with more web-application projects. These projects are more or less independent "modules". One project should be a kind of frame application with shared masterpages, an shared sitemap and and a shared authentication. Later it should also be maybe possible also to integrate loosely older websites (which where written in classic ASP. ASP.NET 1.1, ASP.NET 2.0), but this not so important at the moment
Can you point me to a url for the proper directory structure to create for a new website?I can create a website project and add class library projects to the solution to create a fully functional website.My grey area is that I need to zip up the web site solution and hand it over to the client.I'd like to make sure that I hand over a solution with the most proper directory structure.I'll run you through a scenario:
1. Select File > New > Web Site > ASP.NET Web Site from the main menu 2. Save with a path of C:ProjectsTestWebSite 3. Right-click the solution in VS and select Add > New Project > Class Library 4. The new class library is added with an automatic path of C:ProjectsTestWebSite (2)MyClassLib1
It seems like there should be a way to create a better structure for this but I'm just not following the correct process. Can you point me to a url with instructions for managing a proper structure for this?
I'm working on an application which will store around 50.000 images within it's first year and another 75.000 in it's second. Images can come from Galleries, news images, article images and profile images. So I want to give each image a GUID and store the GUID in the database.As for the directory structure i was thinking of something like this:
So I'm using the first 4 characters of the GUID as my directory structure to spread images a bit more evenly between directories. Now I have some questions about this approach:Is it considered good practice to store all different kinds of images together rather then use ~/Images/Upload/Profiles, ~/Images/Upload/Articles etc.I'm also storing thumbnails and they have a different GUID obviously so the thumbs will not be in the same folder as the original and somehow that doesnt give me a good feeling but I guess it should not matter but.Same goes for Galleries, I'm used to store galleries in folders like ~/Images/Upload/Galleries/12 , and now all the images from a gallery will be scattered around in different subfolders, is this a big performance hit?Do you guys have any other ideas for directory structures?
As you can probably see I'm a bit afraid to use this approach but since there will be lots of images maybe even more then the numbers i gave i have to let the control go I think :)
I am planning to develop an application with asp.net mvc 2. In my project it is very large project.How to plan the solution structure in visual studio 2008. My requirement is module wise solution structure in visual studio 2008 using asp.net mvc2.
I'm looking much more closely at the idea of universal conventions over configuration for my projects (versus 'home-rolled' conventions, or grabbing from a variety of conventions).However, I'm not seeing much, if anything, about the preferred location of ASHX files in, for example, ASP.NET MVC projects (as well as Web forms projects).
Is there a recommended directory structure for these? Perhaps there's a published specification with a much larger directory structure accounted for?My personal convention has been to place these within a top-level Handlers directory, but I honestly haven't personally seen any other projects that really do this.I suppose, depending upon what it does (for example, generating an image), that one could argue this might go into the Content directory, but it seems this directory is generally used for static files.(Aside: One could argue that ASHX files are not needed in MVC projects, but based on questions posted here, it appears ASHX files still have their place in MVC projects.)EDIT: Ignore MVC projects, since I'm suggesting that as one example. How about Web Forms, then?
In above link you clearly describe (How to display directory folder structure). Â
The path only works when the folder insight the project.
When I put folder outside the project it didn't work. What type of changes I need to made to acces the folder outside the poject. & How can I show other details of files which are including in folders Like. Last Modified Created Date, Modified Date etc..
I'm building an application where custom modules may be developed and "dropped in" to the system, where they can be picked up and utilized.
I'm building a forum module and have a user control to create a login/registration region. I plan on using a struct to store the user session data. However, i need this class structure to be shared between the forum module and the login/registration control.
Because the functionality is to be contained in the module's folder, i cant add any assemblies to the app_code folder.
How can i share a class or struct among two user controls?
I am trying to iterate through all the users in a sub node or whatever you call it and get all the users who's lockouttime is not 0. I'm assuming it is 0 if they are not locked out. I can iterate the users but I don't seem to have a grasp of how to use the directory searcher to get a user's lockouttime value. I read so much about how so many conversions have to happen so here is what I have tried.
Using domain__1 As DirectoryEntry = New DirectoryEntry("LDAP://OU=OuP,OU=Ap,DC=urp,DC=yo,DC=dcn", "mydommyid", "mypasscode) Dim mystr As String = Nothing For Each child As DirectoryEntry In domain__1.Children Dim mydom As New DirectorySearcher(domain__1, "(" & child.Name.ToString & ")", Nothing, SearchScope.Base) Dim sr As SearchResult = mydom.FindOne() If sr.Properties("lockouttime")(0) Then Dim mylong As Long = LongFromLargeInteger(sr.Properties("lockouttime")(0)) Dim mylot As DateTime = DateTime.FromFileTime(mylong) mystr += mylot.Date & "</br>" End If child.Close() Next Label1.Text = mystrEnd Usingregards Milton
I have read countless forums and found nothing so for so apparently what I need is an unusual request.I need a code snippet that will iterate through an AD domain account and display all properties for a given user.Has anyone ever built such a script?
If there is a code snippet that displays just the available properties of a user object, this would be sufficient. I am trying to build an application to add users to our LDAP and need to populate all our specific values however I don't have the specific property names to populate.
How to authenticate an user against a particular OU in Active Directory. If the AD holds 50 OUs I don't want to look into all 50 OUs , instead it should look into a particular OU( for eg: OU=dotnet users) to authenticate the user.
How to check if user is part of Active directory or not. I have a username, and i want to check if that user is available in the active directory. I am using .NET 4.0 version
