I've been pounding my head against a wall on this Sharepoint List idea I mentioned a few posts ago. And then, tonight, while, um...on the comode...I had an idea.
All of this stuff is now object oriented. VB is OO, all of the stuff in Sharepoint is OO. I've been thinking in terms of flat development, though, trying to make a project that is generic while also having all of the features I want. Silly programmer.
So, new plan--the sublist stuff will come in the second generation object. First generation will focus solely on keyword processing. Ultimately, the entire goal of a keyword is to drop a value into a list item field. The XML layout for the keywords should contain the keyword name, the column that the value will go into, and a datatype (for validation). I may add one or two things to that list as I work, but that's pretty much it. Then gen 2 can handle processing to sublists based on field values, rather than having it worry about keyword processing as well.
Monday, October 27, 2008
ASP.net Application generating "Parser Error", and unable to find it's underlying object?
This is one of those things that is talked about heavily online--but I hadn't found anything to fix my specific problem. I had a working application that I was able to publish to my development box without any difficulty. I'm just starting to play with web applications, and I can't see to publish to my application server yet, so I took the final product and copied it to it's own folder under wwwroot on the app server.
Every time I went to the app, it said that it couldn't load it's base object. The application DLL was in the application's BIN folder, and I knew it worked. All of the posts I found referring to the error were essentially the equivalent of "Well, did you turn it on?" I was looking for something a little more intelligent.
It turns out that, if you don't use Publish, you have to create the application as well as the folders. Go into IIS Management, find your folder, right click it, and click Properties. Odds are, "Application Name" is set to Default Application, and it's grayed out. Click the Create button, and it will create a new application (named for the folder). This will cause IIS to look in that folder's BIN folder for the DLL, like it's supposed to.
This is one of those things that is talked about heavily online--but I hadn't found anything to fix my specific problem. I had a working application that I was able to publish to my development box without any difficulty. I'm just starting to play with web applications, and I can't see to publish to my application server yet, so I took the final product and copied it to it's own folder under wwwroot on the app server.
Every time I went to the app, it said that it couldn't load it's base object. The application DLL was in the application's BIN folder, and I knew it worked. All of the posts I found referring to the error were essentially the equivalent of "Well, did you turn it on?" I was looking for something a little more intelligent.
It turns out that, if you don't use Publish, you have to create the application as well as the folders. Go into IIS Management, find your folder, right click it, and click Properties. Odds are, "Application Name" is set to Default Application, and it's grayed out. Click the Create button, and it will create a new application (named for the folder). This will cause IIS to look in that folder's BIN folder for the DLL, like it's supposed to.
Saturday, October 25, 2008
Tried to update our oldest SQL 2005 box to SP2 this morning, and the update of the database and analysis services failed. Nothing too obvious in the log. During the middle of the SP install, I got this error twice:
Installation of KB921896 Failed.
I'll spare everybody the hour or so of blog reading; here's what I ultimately found:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=378205&SiteID=1
This server was originally just a member server, but I upgraded it to a Domain Controller (long time ago, back when I had very limited server resources). The security groups that the post at microsoft.com refers to were deleted at DC Promotion. Removing the registry entries mentioned in the post worked great.
Installation of KB921896 Failed.
I'll spare everybody the hour or so of blog reading; here's what I ultimately found:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=378205&SiteID=1
This server was originally just a member server, but I upgraded it to a Domain Controller (long time ago, back when I had very limited server resources). The security groups that the post at microsoft.com refers to were deleted at DC Promotion. Removing the registry entries mentioned in the post worked great.
Saturday, October 04, 2008
Huh, they haven't deleted this thing yet. OK, so here's my big "what if" project right now. I'm starting to hit Sharepoint pretty heavily for work, and I want to do a big whiz-bang thing to show management so they realize the benefits. I also want to start tracking support calls better.
So, in a nutshell, here's the plan: Create a list on a sharepoint site that will receive all of our support emails and voicemails. Have this list use the ID number of the list entry as a case number, and have the list use keywords included in the posting to set various items (like responsible IT person, issue types, etc.).
Then, have another list that contains the work detail for each case. I'm thinking that I can put logic into the first list so that, if a posting comes in that has a case number keyword embedded in it, it can move the entry to the secondary list as a piece of detail for that case.
I'm playing around with event receivers for lists (I'm using the announcement list right now--seems simplest), but I'm missing one somewhat important piece. The primary list will need to have a reference to the secondary list in some way. I figured I'd just use Visual Studio to create a new list type based off of Announcement, but all I can do with that is add columns to the list. I haven't found yet if I can add properties to the list itself. So if anyone knows how to do that, let me know--otherwise my workaround will be to put one entry into the list (expire it, since I'm using the announcement list and it won't show up on most views if it's expired) that has keywords for the name of the secondary list, as well as any other "List wide" properties I need.
So, in a nutshell, here's the plan: Create a list on a sharepoint site that will receive all of our support emails and voicemails. Have this list use the ID number of the list entry as a case number, and have the list use keywords included in the posting to set various items (like responsible IT person, issue types, etc.).
Then, have another list that contains the work detail for each case. I'm thinking that I can put logic into the first list so that, if a posting comes in that has a case number keyword embedded in it, it can move the entry to the secondary list as a piece of detail for that case.
I'm playing around with event receivers for lists (I'm using the announcement list right now--seems simplest), but I'm missing one somewhat important piece. The primary list will need to have a reference to the secondary list in some way. I figured I'd just use Visual Studio to create a new list type based off of Announcement, but all I can do with that is add columns to the list. I haven't found yet if I can add properties to the list itself. So if anyone knows how to do that, let me know--otherwise my workaround will be to put one entry into the list (expire it, since I'm using the announcement list and it won't show up on most views if it's expired) that has keywords for the name of the secondary list, as well as any other "List wide" properties I need.
Subscribe to:
Posts (Atom)