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

More Search Options

RSS Available

• I don't think this is an answer to my question

  I know that you can run managed code from SQL 2005 triggers, but the " //C# communication code here" is what i'm wondering about. Would that be the service broker? or TCP/IP? or what?

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by wildert on 3/23/2007

• Communicate with Service Broker in C#?

  So SQLDependencies failed to do what I wanted them to do for my Cache Invalidating, so i'm going to humor another possibility for a half day - Triggers on my database table that communicate messages to my C# inside my ASP.NET App. Any advice on how to tap into a message queue with C#? I'm thinking that my messages could be 1 of about 100 different strings as far as what occurred on the Database Tables

  Posted to SQL Server, SQL Server Express, and SqlDataSource Control (Forum) by wildert on 3/22/2007

• Re: SQLDependency accuracy

  In my google meanderings i've found other people complain about this same issue, the query doesn't do anything, you will always get all changes from the entire table. Next approach...possibly Triggers and tapping into the Service Broker through C#?

  Posted to State Management (Forum) by wildert on 3/22/2007

• Re: SQLDependency accuracy

  I am using SQL 2005. connection = new SqlConnection ( "my_connectionstring" ); connection.Open(); command = new SqlCommand ( "Select Authors from dbo.Books" ,connection); dependency = new SqlDependency (command) ; dependency.OnChange += new OnChangeEventHandler (dependency_OnChange); SqlDependency .Start( "my_connectionstring" ); reader = command.ExecuteReader(); this is the code I use, the OnChange event files whenever any change occurs to the database table. What am I doing wrong?

  Posted to State Management (Forum) by wildert on 3/21/2007

• SQLDependency accuracy

  I am curious what the point is of actually creating an SQLCommand object and specifying a select statement, because my SQLDependency Onchange event fires no matter what column is changed in the Table I use for the Select Statement. For example, If I have a Books table with columns Author, Title and my select statement is "Select Authors from Books", a change to a rows "Title" column will cause the SQLDependency to fire. is there a way to figure out which columns changed? I know I can determine changes

  Posted to State Management (Forum) by wildert on 3/21/2007

• Re: Dynamic Website Architecture

  So I think another answer (this was my own question) is that ASP.NET doesn't give good facility to add/remove pages and that functionality is found only in Portal frameworks (I've read places that WSS / sharepoint is basically an XML driven VirtualPathProvider), so thats the answer I believe to be true. I'm using a VirtualPathProvider and another place on my filesystem right now, and probably will remake my app in sharepoint soon.

  Posted to Architecture (Forum) by wildert on 3/17/2007

• Re: Allow custom Webpart to write to FileSystem

  Yes this is correct, My problem was that while dev'ing on the VS2005 web server it uses the admin account which has full trust, but when thrown into IIS its a much more restricted account.

  Posted to Windows SharePoint Services Hosting (Forum) by wildert on 3/13/2007

• Dynamic Website Architecture

  So I'm creating a website where users can create webpages and then sub-webpages and on and on. so I have the scenario where a user starts at Home.aspx and creates Page1.aspx and then later on Page1/Subpage1.aspx. My first inclination was just to use System.IO classes to create/remove aspx's within my IIS directory, but the Session variable seems to reset on any filesystem change. So now a virtualPathProvider is the only way I know of to dynamically create/remove aspx's, and they aren't exactly easy

  Posted to Architecture (Forum) by wildert on 3/13/2007

• Re: handle button events in formview

  I came to a similar conclusion (though I was very surprised I had to call databind each time I wanted the FormView to databind, I thought it would re-databind on each postback. Important note on more difficult scenarios, you can find out what even caused a postback anywhere anytime using the Request.Params collection. examine the EventArgument and EventTarget objects for all controls except buttons. because buttons are always submit buttons, they are handled individually and you need to examine each

  Posted to Data Presentation Controls (Forum) by wildert on 2/25/2007

• Re: handle button events in formview

  I came to a similar conclusion (though I was very surprised I had to call databind each time I wanted the FormView to databind, I thought it would re-databind on each postback. Important note on more difficult scenarios, you can find out what even caused a postback anywhere anytime using the Request.Params collection. examine the EventArgument and EventTarget objects for all controls except buttons. because buttons are always submit buttons, they are handled individually and you need to examine each

  Posted to Data Presentation Controls (Forum) by wildert on 2/25/2007