identity

On our Windows 2008 R2 server I have a site running under the default ASP.NET v4.0 application pool. The identity of ASP.NET v.4.0 app pool is set to "ApplicationPoolIdentity" (I guess this is default). How do I grant this identity access to read from a custom folder within my site. I have tried "Application Pool Identity" and "ApplicationPoolIdentity" but both gives me: An object named "Application Pool Identity" cannot be found. Bonus question = should I instead forget about all this and make the change to store the files in app_data folder? Would that solve the issue? karlm ICACLS <folder>

I was wondering how can I add an identity column to existing oracle table? I am using oracle 11g. Suppose I have a table named DEGREE and I am going to add an identity column to that. FYI table is not empty. You can not do it in one step. Instead, Alter the table and add the column (without primary key constraint) ALTER TABLE DEGREE ADD (Ident NUMBER(10)); Fill the new column with data which will fulfill the primary key constraint (unique/not null), e.g. like UPDATE DEGREE SET Ident=ROWNUM; Alter the table and add the constraint to the column ALTER TABLE DEGREE MODIFY (Ident PRIMARY KEY);

I have one question. I'm trying change error message in Identity ASP .NET and I don't know how do it. I want change error message - "Login is already taken". CreateAsync method return this error message. Please help me. The Microsoft.AspNet.Identity.UserManager<TUser> class has a public property called UserValidator of type IIdentityValidator<TUser> . The constructor for UserManager sets that property to an instance of Microsoft.AspNet.Identity.UserValidator<TUser> . The error messages you see when calling CreateAsync come from the resources embedded in the Microsoft.AspNet.Identity.dll and

I'm in the process of designing a fairly complex system. One of our primary concerns is supporting SQL Server peer-to-peer replication. The idea is to support several geographically separated nodes. A secondary concern has been using a modern ORM in the middle tier. Our first choice has always been Entity Framework, mainly because the developers like to work with it. (They love the LiNQ support.) So here's the problem: With peer-to-peer replication in mind, I settled on using uniqueidentifier with a default value of newsequentialid() for the primary key of every table. This seemed to provide a

In SQL Server 2000 or above is there anyway to handle an auto generated primary key (identity) column when using a statement like the following? Insert Into TableName Values(?, ?, ?) My goal is to NOT use the column names at all. Eric By default, if you have an identity column, you do not need to specify it in the VALUES section. If your table is: ID NAME ADDRESS Then you can do: INSERT INTO MyTbl VALUES ('Joe', '123 State Street, Boston, MA') This will auto-generate the ID for you, and you don't have to think about it at all. If you SET IDENTITY_INSERT MyTbl ON , you can assign a value to the

We are using a custom principal and identity type (ProdigyPrincipal/ProdigyIdentity) because we need extra information within our programs and services. In the program we set the principal and identity. When communicating with a WCF service the principal and identity are set, but after casting to our own type the principal and identity are null. I noticed that there is a difference between running in Debug mode and Unit Test mode. In Debug mode the type of the principal and identity are of type WindowsPrincipal and WindowsIdentity . In Unit Test mode the types are GenericPrincipal and

Is using MS SQL Identity good practice in enterprise applications? Isn't it make difficulties in creating business logic, and migrating database from one to another? James Yes, they work very well and are reliable, and perform the best. One big benefit of using identity fields vs non, is they handle all of the complex concurrency issues of multiple callers attempting to reserve new id's. This may seem like something trivial to code but it's not. These links below offer some interesting information about identity fields and why you should use them whenever possible. DB: To use identity column