On the off chance that someone else will encounter the same errors, I'm posting the problems I'm encountering in this upgrade.
After hearing about Google's new GMail product, where email is "categorized" instead of just jammed into folders, I was thinking it would be neat if you could do the same thing with files in the Windows file system.
Basically, you'd need a way to index the existing files, categorizing them according to the user's needs. For example, one Word document may be categorized in the 'Word documents', 'Code fragments', 'Memos', and 'Development Team' categories...instead of just getting filed away in 'My Documents' under, at best, a folder representing one of those categories.
The beauty of this would be in searching. Besides the usual 'search by name' junk, you could restrict a search to certain categories. (think...“I know I sent that code fragment in a memo to the whole development team“)
Using Google, I looked around for such a thing and found that Microsoft's Longhorn is packaged with exactly what I'm dreaming about: they call it WinFS and the article that dashed my dreams of fame and fortune is here.
I noticed this post from Ed Daniel a few days ago, but didn't get a chance to check it out until today. I really dig the format (short video interviews, quick and to the point).
A current Windows Forms project of mine requires the caching of a fair amount of data. Specifically, I want to store, in memory, on the client, a selection of XML data. When it's done, this should behave something like ASP.NET's session object...so I'll have access to user information and preferences without having to hit the data source every time to get it.
It's no problem to instantiate a class that retrieves and holds this information, but making that information available to other forms in the application (without again reloading an instance of the class and re-retrieving the data) is escaping me. I explored Microsoft's Caching Application Block, and while it appears to offer the kind of behavior I'm after, it's a bit more complicated than I need (and depends heavily on SQL Server...I want to avoid that).
Anyone have any suggestions out there?
It's a little like watching the neighbor kid grow up...a year ago, a Google search for 'Rainbow portal' would hit on rainbowportal.net, and not much more.
Now, you get pages and pages of hits, including this one and this one, which offer special Rainbow hosting packages. I can't wait to see those results next year, with a v1 release behind us and .Next getting rolling.
I agree with this guy...who agrees with this guy...
Although, as I look around, I have five different 'Teach yourself/Learn X in Y days/Hours' books on the shelves. *blush*
Every time I restart my XP Pro laptop, it downloads the same update (KB835732) and asks to install it.
Reference to an interesting article that tries to draw some conclusions about whether Diabetes is related to certain structural patterns of the ridges in the palms of the hands.
Browsing Google search results for 'fingerprint blog', I ran across this entry on an adoption site, where subject was told his prints 'failed' because
“Some people just have bad prints that can't be recorded at the level required to read them effectively.” While this is not impossible, it's very unlikely, and a few comments on that entry had also been given bad information. I felt obligated to post a comment myself:
“Fingerprints vary in quality from person to person, but it's likely that yours are fine (meaning, OK).
Generally speaking, 'blue collar' type workers (i.e. stone masons, builders) can have terrible fingerprint ridge structure...they're constantly wearing off the skin that forms the ridges. The same is also true for folks (again, generalizing) who shuffle a lot of paper (i.e. bank tellers, envelope-stuffers), because the paper has a similar effect.
In the *vast* majority of cases, though, bad recording of fingerprints is due to operator error...and the quality produced by ink/paper (done properly) still beats any computerized recording system in existence.”
I heard this exchange in the doctor's office last week:
Patient (walking back for his Vasectomy procedure): “Hey Doc. I hope you got a good night's sleep.”
Doctor: “Yep, I did. But I've been drinking all day.”
Our vacation stay at Villa Poincianna in the Abacos was really terrific. The house was amazing...remote and quiet, but a short boat ride from everything we wanted.
We got to see a good mix of sea critters (sharks, turtles, 'cudas, rays, and plenty of other fish) while snorkeling. Also, I was surprised at how 'un-touristy' the whole area was...no one bothered us to buy trinkets or bracelets (yes, that's what I expected) and local people were genuinely interested in helping us.
The stay wasn't perfect. Weather in the Abacos is apparently as uncontrollable as weather here in Michigan, and we ended up with high winds (and seas) the whole time. No matter, we were snorkeling and boating in it every day. The ride to Pete's Pub was especially interesting.
Being new to the whole blogging thing, I'm still learning what exactly this application is doing with my rambling text. I've noticed that many of the hits on this blog are rss aggregators (mostly from rssreader.com), and this article has now explained that concept.
I like the idea of getting all the news I care about brought directly to me...I wish I'd thought of that.
Tomorrow afternoon, we're heading out for Lubber's Cay in the Abacos for our first no-kids vacation since our honeymoon (in spring 1997). Seeya in a week or so!
In a post last week, I complained that one of my Rainbow installations was hung on the update screen with the 'Your Database is up to date' message. I found a solution (work-around, really), but more explanation is in order first.
I had backed up a production database onto a local server, then tried running the update. This backup had been made by copying the production data over an existing database, with the data copy mode set to 'overwrite'. This is the scenario that caused problems.
I ended up wiping out all tables in the local database, then running the data transfer again from the production site to the local one. When I ran the update against this new local DB, it went just fine.
So, I solved the problem...but I don't really know what it was...or something like that.
I've noticed that sometimes Visual Studio .NET 2002 hangs when I try to delete a file or files from the 'Solution Explorer'. It just gets stuck on 'deleting file' dialog, and I have to close it with the task manager.
Is anyone else seeing this, or am I just really lucky?
In trying to update a Rainbow installation from v 1756 to 1757, I'm stuck with the message 'Your database is up to date'
I've been wanting to hook up a webcam, mostly so my PC can stare back at me while I work and partly so acquaintences I've made around the globe can put a face (mine even) with a name.
I spent the big bucks ($29.95USD) on a LabTec WebCam and installed it (and its accompanying software) on my Toshiba Satellite A35-S159 running Windows XP.
Immediately, Internet Explorer no longer could find the Internet. I eventually rebooted the machine, and then couldn't even load Windows properly. I was just stuck with a mouse icon that would hourglass when I passed anywhere over the Taskbar or Start Menu. I tried to uninstall the camera software, but the applications list wouldn't enumerate...it just hung there, and rebooting several times didn't help either.
Windows XP saved me with its Restore Points feature. I went in there the next day, and it had a point saved for the moment before the camera was installed. I ran the Restore wizard, and it worked like a charm. Thanks Microsoft!
It's kind of creepy for a computer to be able to see you anyway, right? I wonder if KMart will give me my money back...
Update: I'm not the only one with USB web cam problems...click here.
Plagued by yet another weird error...
Unable to create the web project “myProject”. Unable to validate that the file path ‘c:\inetpub\wwwroot\myProject’ matches the URL path ‘http://localhost/myProject’. A connection with the server could not be established.
I started getting this error any time I tried to open a web project in Visual Studio .NET...even projects I had opened successfully before. In searching around, someone suggested a firewall may be to blame. I turned off McAfee Firewall, and presto, it works fine. Who needs protection, anyway?
Jeremy took pity on me and had a glance at a sample project I was using to test eXist with SOAP. It seems Visual Studio .NET's 'Add Web Reference' Wizard wasn't setting up the proxy class for the web service correctly...
The web services are at http://localhost:8080/exist/etc... but VS.NET set up the proxy classes to use http://localhost/exist/etc... Manually adding the ':8080' to the web references' server name completely resolves the connection problems I was having.
I am working on a project that requires importing a large amount of data from 'text data files' that were originally created with QuickBasic (in the 1980's). One (not-so-quick) lesson I've just learned...that old text isn't written with ISO, UTF, or even ASCII encoding. It's windows-1252.
The problem showed up when trying to convert a two-bit string into an integer (the pointer to a related record) with the CVI() function. Those funny little non-usual characters don't come through correctly with any other code page...
With a simple line:
Encoding encoding = Encoding.GetEncoding(1252);
Everything works.
I ran across this great article that gives a quick, clean example of how to export a web page's DataSet to Excel. What's nice is that this example doesn't use a second web form for the export...it just re-uses the Response object in the current form. Very handy!
http://www.dotnetjohn.com/articles/articleid36.aspx
|