You searched for the word(s): userid:635583

More Search Options

RSS Available

• Problem with content page title

  Hello everyone, When I'm developing a site using ASP.net 2 Master Pages I usually define the title in the master page so it doesn't have to be repeated every single time. In the content pages, inside the PAGE declaration I delete the Title property, so it doesn't override the already defined value. On the browser it works great. The problem is that the generated code is not compliant with XHTML 1.1 standards. Here's the code that is generated: 1 < head > 2 < title >MyTitle<

  Posted to Master Pages, Themes and Navigation Controls (Forum) by DBA on 11/26/2007

• Re: Question regarding application design choise

  Thanks everyone for your replies. I'm inclined to try what you are suggesting StevenPaul. It seems like the it is the simpliest way to acheive what I want. Should I run into more troubles I'll let you guys know :) Best regards.

  Posted to Architecture (Forum) by DBA on 8/29/2007

• Question regarding application design choise

  Hello everyone, While developing a multi-platform (web, desktop, mobile) application I'm having some trouble deciding what's the best way to reduce the coding process. My objective is to share as much functionality, as possible, between all of the platforms, ultimately meaning that my objective is that each of the platforms only contains the presentation code. Since this application is to be available in several platforms, I thought that it would be of great use to create a central webservice

  Posted to Architecture (Forum) by DBA on 8/28/2007

• Ambigous name problem when using a custom API

  Good afternoon everyone, In the process of developing an application, for the company I work for, I've figured that the best way to resue the business logic accross the 3 different interfaces would be to create an API with all the business objects, business logic and data access stuff. In the end it would look something like this: [Interface] -> [API Remote Web Service Proxy] -> [Remote Web Service] -> [API Business Logic] -> [API Data Access] -> [<-- All the way back] My idea

  Posted to Getting Started (Forum) by DBA on 8/24/2007

• Re: Problem when adding cascade actions to a relationship

  [quote user="TATWORTH"] Instead of using a cascade, why not either write the delete into your stored procedure or usea logical delete flag? [/quote] Thanks for your reply Tatworth. It's only because that would make me have half the app with cascade and the other half hand coded. Before I consider that solution I'd much rather understand why this error is being returned and to know if there's any design change I can put in place to fix it.

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by DBA on 8/21/2007

• Problem when adding cascade actions to a relationship

  Hello everyone, I wanted to change a relationship in a database in order for it to have a cascading effect on update and on delete in order to preserve the data integrity. The problem is that when I click the save button I get the following error message: 'Role (Application)' table saved successfully 'Usergroup_Role (Security)' table - Unable to create relationship 'FK_Usergroup_Role_RoleId_Application_Role_Id'. Introducing FOREIGN KEY constraint 'FK_Usergroup_Role_RoleId_Application_Role_Id'

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by DBA on 8/21/2007

• Re: Architectual problem

  [quote user="Imco"] Hi DBA, Glad I could help. I wasn't entirely sure if I was actually going to post that whole thing but I figured I might as well since I did all that typing. ;) I like the ease of that approach. It's fairly straightforward to implement and should be easily understood by someone asked to maintain it. I did some experimentation about six months ago along the same lines. I wrapped the existing asp.net providers for roles memberships and profiles with a thin layer

  Posted to Getting Started (Forum) by DBA on 7/11/2007

• Re: Architectual problem

  Hi Imco, actualy your answer was pretty useful. That was exactly what I was looking for with my last question. I'm considering to create a centralized app that will only handle membership and eventualy roles. This application would also keep track of all other applications that are using the membership database, handeling all the stuff through a simple web service. The idea is simple and cheap, in theory. When an application wants to use the membership database it "signs" for the service

  Posted to Getting Started (Forum) by DBA on 7/9/2007

• Re: Architectual problem

  Still my question stands, how do you keep an integretity across the applications. Ok, you put all the user stuff in one database and use the user id in the other application databases. But what if you delete a user from the user database? How do you propagate that across all application databases? Is it possible to create a relationship as if it was two tables? Do you need a middle tier application?

  Posted to Getting Started (Forum) by DBA on 7/9/2007

• Re: Architectual problem

  [quote user="TATWORTH"] If all the web sites share a common server, put the membership functionaly into a web service site on the same server. (The web service can be locked down to repond only to the local sites.) [/quote] My original idea was to do just that. I just have one question about that approach. Let's imagin we have application A (main) and application B. In application A we have a database table called Members which is exposed through application's A webservice. With

  Posted to Getting Started (Forum) by DBA on 7/9/2007