Steve Saxon's Downtime: Unanswered Threads

seeking source for ganguro picture from June 2004

ganguro — Sat, 23 Jun 2007 01:30:35 GMT

Hi, there,

I''m looking for the source of one of the ganguro pictures you used when you discussed the ganguro trend in Japan back in 2004. It's the photo on the right and I'd like to use it in an academic article I'm writing. I notice that you've included a link to the livemusicstudio site, but the photo in question does not appear to be from the picture gallery on that site. Any leads? I need to get this information quickly as my article is to be published soon and I really want to include this photo, if possible. The journal I'm working with wants copyright clearance. Thanks! .

Thanks!

Ganguro (researcher)

runit tries to load assemblies from IDE folder

labcoatguy — Fri, 20 Apr 2007 19:47:38 GMT

Hey Steve,

I've been trying to get runit running with a project I'm working on, but I get a run-time error. Runit tries to load the DLLs/assemblies listed in my web app's bin folder, from the Visual studio IDE folder (they aren't there), e.g.:

+ [System.IO.FileNotFoundException] {"Could not load file or assembly 'C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\IDE\\DictionaryConfiguration.NET2.dll' or one of its dependencies. The system cannot find the file specified.":"C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\IDE\\DictionaryConfiguration.NET2.dll"} System.IO.FileNotFoundException

In this case, DictionaryConfiguration.NET2.dll is the first file in my app's bin folder.

Any tips?

Thanks,

Mike

Need to change version number string

tlmurray — Tue, 06 Feb 2007 19:23:23 GMT

The download page says iComic is 3.03 -- but the version (as shown in Get Info and the version column in the Finder) shows a longer string and 3.0.

So, in the spirit of proper Mac programming, my suggestion is to place just the numeric version 3.03 in the proper string position.

Thanks.

Querying Active Directory using LINQ

xmlguy — Mon, 23 Oct 2006 01:20:18 GMT

At Desert Code Camp in Tempe AZ on October 28th I will be giving a talk on how to write an extender that lets you query Active Directory using LINQ.

At that time I will post the code here for folks that would like to try it out for themselves.

Here are examples of queries written using my LINQ extender:

// find the names of all people in AD whose last name is Smith or first name is John
var q = from e in AD.Users where e.LastName == "Smith" || e.FirstName == "John" select e.Name;

This query ends up querying Active Directory with this filter:

(&(objectCategory=user)(objectClass=person)(|(sn=Smith)(givenName=John)))

For comparison, the traditional System.DirectoryServices API equivalent of this query is:

List<string> q = new List<string>();

using(DirectorySearch searcher = new DirectorySearcher())
{
searcher.Filter = "(&(objectCategory=user)(objectClass=person)" +
"(|(sn=Smith)(givenName=John)))";

    foreach(SearchResult result in searcher.FindAll())
    {
        q.Add(result.Properties["name"][0].Value);
    }
}

As you can see, the LINQ based query is much easier to read!

You can also do membership-based queries such as this one:

// get the name and email of everyone in the group called Western Region
var q = from e in AD.Groups.Single(g => g.Name == "Western Region").GetMembers()
select new { e.Name, e.Email };

Before anyone asks, my example does not currently support making changes back to the repository.

Getting Community Server 2.1 running on GoDaddy

xmlguy — Sat, 07 Oct 2006 14:34:24 GMT

There are a few things you will need to know if you are wanting to get Community Server 2.1 up and running on GoDaddy.

Get the Community Server 2.1 Web Install
Get supaleet's Instructions for installing CS2 on GoDaddy

The second of these is good for the info on how to create the initial database, get the Community Server files FTP'd up there and repointing the database.

For the database setup itself you should use the SQL scripts that came in the Web Install.

The biggest problem as it turns out is that GoDaddy's "Query Analyzer" (the tool they use to perform DDL operations on the database) barfs on any remotely complex SQL, including the CS 2.1 SQL scripts.

I wasn't going to let that slow me down, so I wrote a mydb.aspx page that let me set up the database myself using the same .sql files.

To use this tool, first make sure you have all of supaleets FTP and database re-pointing instructions done (by repointing I mean ensure that your web.config has all the database connection strings pointing to the database that GoDaddy made for you).

Before you can run the Community Server creation script you will need to run the aspnet_regsqlOn tool to build the ASP.NET 2.0 SQL setup script. To do this, go to a command prompt and type:

CD /D %systemroot%\Microsoft.Net\Framework\v2.0.50727
ASPNET_REGSQL -A all -d db_##### -sqlexportonly aspnet.sql

The ##### should be replaced with the number GoDaddy gave you when the database was created. You will also see this number of the connection string from following supaleet's instructions.

Once you have this, FTP the mydb.aspx script together with the aspnet.sql script to the root of your Community Server web site at GoDaddy.

You should also upload the cs_2.1_createfulldatabase.sql file to the same location. I renamed mine to create.sql to make it easy to remember later.

Next you should rename the web.config and global.asax files at your GoDaddy site. I put a "_" at the end of mine. You will want to create a copy of the web.config on your local PC and edit it to not include any of the httpmodule or httphandler information, nor any of the setup for profiles, roles or membership. Upload this modified web.config into your FTP site. We do this to prevent ASP.NET from trying to use any Community Server or ASP.NET database features before we have the new databases set up.

You're now ready to create the database. In the browser run the following:

http://www.yoursite.com/mydb.aspx?sql=aspnet

You should see a bunch of records saying "# records changed".

If all goes well, run the following:

http://www.yoursite.com/mydb.aspx?sql=create.sql

(remember this is the CS 2.1 createfulldatabase script which I renamed to make it easier to remember at this stage).

Again, it should all work well.

Now to clean up. Delete the mydb.aspx, the two .sql files and the reduced web.config from your server via your FTP client. Once that is done, rename the global.asax_ and web.config_ files back to their original names without the trailing underscore.

The last step is to exec the stored procedure to set up your CS site, per the instructions in the web install, which you can do via GoDaddy's Query Analyzer.

Best of luck!