| |
 |
Sunday, April 27, 2003 |
Changing my Category from "My Learning About Radio" to "My Blogging Software"
Google Search It
Since I took the time to get BlogX running the natural place to post the pains of the process was in my about blogging category. However, since this was previously called "My Learning About Radio" I decided a name change was in order. Welcome to the "My Blogging Software" category.
11:56:39 PM
|
|
"This is a simple BloggerAPI client for PocketPC's, that can be use to edit and create posts for weblogging tools that support the BloggerAPI such as Blogger and Radio."
11:53:21 PM
|
|
Here are a couple things I learned from reading Rockford Lhotka's excellent article on data binding:
- "When we bind controls on a form to properties of an object, data binding listens for propertyChanged events for each property to which our controls are bound. If any one of them is raised, all the controls bound to that object are refreshed. The downside to taking advantage of this fact is that the UI becomes tightly bound to the object implementation. If we later decide to only bind to Amount, our UI won't work correctly because no AmountChanged event will be raised. Because of this, it is best to declare and raise a propertyChanged event for each property on our object."
- A full implementation of IEditableObject will privide a mechanism to roll back changes for a particular object. This provides built in support for cancelling out of a properties dialog for example.
- Use IDataErrorInfo to handle validation on a particular item. Unfortunately, the granularity is at the item level not the property within the item. Therefore, it cannot handle providing information on multiple problems with a particular IEditableObject.
10:47:32 PM
|
|
No, you can't turn off the garbage collector but here are some things you can do to reduce the likelyhood that it or the finalizer thread will run.
8:26:18 PM
|
|
In an attempt to consider an ASP.NET based bloggar I joined the BlogX workspace on GotDotNet. Unfortunately, getting started was not nearly as easy as I would have liked. Here are the steps I took including the things that didn't work.
- Ran Win WeblogX Setup and got the following error: Installation Incomplete - The Installer was interrupted before Blogx0.1 WeblogX could be installed. You need to restart the installer to try again.
- Followed manual instructions located in the readme.html file but:
a) Step 3 does not indicate what permissions to provide on the virtual directory. I assume Read/Write? Also, I created the virtual directory via the Security and Sharing menu on Windows Explorer, not through IIS which I presume is okay?
b) In step 4 there was not Content or Logs directory. I created them manually in the same directory as the SiteConfig directory.
c) After selecting "Create New" (not create new server) in WinBlogX an exception was thrown: "The request failed with HTTP status 401: Access Denied."
- Ran WinSetup and got the following error: Installation Incomplete - The Installer was interrupted before Blogx0.1 could be installed. You need to restart the installer to try again.
- After deleting the Vitual Directory that I created in 2a (above) I opened up IIS and created the virtual directory manually giving it read, script, execute and write permissions (note to self....remove write and execute once everything is working).
- Gave IUSR_<ComputerName> Read & Execute, List Folder Contents, Read, and Write permissions on the Content, Logs and SiteConfig directories (Content and Logs directories were created manually back in step 2b).
- Re-ran WinBlogX and got an unhandled exception: "Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'."
- Retrieved an updated copy of the source code but on attempting to compile I found I was missing the IsolatedUserSettings.cs and WMPCForm.cs files from the WinBlogX project. Grrrrrr!! (Sent email to the last person that checked in the csproj file to see if they could fix it.)
- I removed references to the offending files and modified the code so that it compiled again.
- Re-running WinBlogX prompted me to save a winblogx file which I did. I was then prompted with a dialog entitled "Annoying wait dialog." The dialog included a counter and a kill button. Unfortunately I waited until the counter reached 600,000 but it still didn't go away. I resorted to the Kill Program button on the dialog.
- Restarting seems to have loaded WinBlogX correctly so I proceeded to add a post.
- After posting the same "Annoying wait dialog" appeared so I killed the program. Again, on restart the post seems to have worked and appears when I go to the WebLog site.
Certainly far from smooth but at this point I will consider BlogX setup.
6:14:50 PM
|
|
InspectExe is integrated directly into the Windows® Explorer and adds as a set of extra pages in the Properties sheet to display the imported and exported functions of the executable file (.EXE, .OCX or .DLL) as well as the embedded resources.
5:45:21 AM
|
|
© Copyright 2004 Mark Michaelis.
|
|
