My ASP.Net intellisense was gone!

I use Visual Studio 2008 at work on a remote terminal server.
This server doesn’t have enough disk space on its C drive, and VS2008 likes to place a lot of ReflectedSchemas there.
It got to the point where I has some 4GB of ReflectedSchemas and this was too much, so I deleted them all (nice and definitive) and things were great again.

A couple of weeks later the exact same thing happened again, so I deleted them again, this time though I noticed that my Intellisense for the standard ASP.Net controls (like ) was gone! Still had it for other (custom) controls and HTML tags and everything, just not ASP.Net controls.

Today finally I decided to look into it (2 or 3 months later).
I got a tip to try devenv /ResetSettings, which didn’t help.
One person suggested you change the tag prefix, which also didn’t help.
I also tried copying someone else’s ReflectedSchemas, which still didn’t help, though this could be explained perhaps by the fact that I didn’t overwrite the entries.xml, I don’t know.
After this I tried deleting the ReflectedSchemas again, this time making 100% sure that I had closed devenv.exe. This fixed it…

So now I am enjoying my ASP intellisense once again.

Enabling/Disabling Services in Fedora 12

I have been having trouble with my sshd service.
I use SSH to log in to my home computer and manage things like the hours I work and such, and sometimes when I restart my computer I forget to turn it back on.

But thanks to this site I figured out how to manage services from the command line and now I’ve set both sshd and httpd to start at start-up. Which makes it easier.

But to sum up:
Log in as root with su and then run chkconfig --list to view which services are enabled at which runlevel (runlevels are explained on the linked page). Then to enable services use

chkconfig --level 35 sshd on

specifying runlevels 3 and 5 here and turning the sshd deamon on.

This helps me, now I can’t forget to turn on sshd and my boss won’t have to fear that I might not be able to log in to my home computer so much anymore.

First Post

As always some things just need to get done. A first post is such a thing!
I already have a blog and I occasionally post there, but since we’re going to be using wordpress at work now I thought I’d make me a blog here to get familliar with things.

Gnome-shell in Ubuntu 9.10

Even though gnome-shell is really only a preview of what is to come for gnome 3.0 and it’s still buggy and sometimes not completely stable perhaps, I really like it.

When I first saw the screenshots I was less then impressed, I thought it didn’t at all look like anything new or innovative, but rather messy and confusing. But me being ever interested in new things and all I just had to give it a try (the gnome-panel look was starting to bore me).

Installing was easy

sudo apt-get install gnome-shell

and starting it afterwards was easy too

gnome-shell -r

Though first I had to disable compiz, which I don’t really use anyway.
I was also using avant-window-navigator, which disappeared on me but still kept part of my notification area to itself. So the time after that I first closed AWN and all was as it should be.

I didn’t feel like having to manually start gnome-shell every time I logged in so I started looking into a way to replace metacity and gnome-panel with gnome-shell and found that this could be done by editing you gconf (with, for example, gconf-editor) and setting the /desktop/gnome/session/required_components/windowmanager key from metacity to gnome-shell.

Of course, since it is a composited window manager you need a video card and driver that can handle screen compositing.

mod_rewrite with Fedora 10 and ISPConfig for WordPress

This relates to Fedora 10 and ISPConfig 3.0.1 set up as described in this HowtoForge post

One of my colleagues recently got interested in offering our clients WordPress as a content management system, so he’s been trying it out.
Yesterday he found out that if he wanted to change the permalink style in WordPress he needed write access to .htaccess, which he didn’t have because the user rights haven’t been set up very well there.
So I gave him write access by using

chown apache:apache .htaccess

Unfortunately this resulted in a 500 Interal Server Error.
Looking at the error log for the website I tried this for it let me know that RewriteEngine directives were not allowed in the .htaccess.
Since I didn’t want to mess with the base configurations of ISPConfig I started looking around for other options. Eventually I found that I had to add something similar to this to the Apache directives field under options under the website’s settings

<IfModule mod_rewrite.c>  <Directory /var/www/[sitename]/web/>    Options +FollowSymLinks    RewriteEngine On    RewriteBase /    RewriteCond %{REQUEST_FILENAME} !-f    RewriteCond %{REQUEST_FILENAME} !-d    RewriteRule . /index.php [L]  </Directory></IfModule>

Of course [sitename] should be replaced with the name of your website.

It all works after I restarted the apache server myself, but I do not know if that is completely necessary. Also it might take a few seconds before ISPConfig finishes editing the configuration file.

Higher Resolution in Fedora 11 with proprietary NVidia Drivers

Ugh… I have been screwing around with this since the beginning of time… Or at least since I installed Fedora for the so-manieth time. Finally though I found out what I had to do.

Following this guide, I was able to easily and correctly install the drivers. I used to build them myself, but that got me worse results then anything.
To sum up, though:

# switch to super user (root)

# install rpmfusion repository
rpm -Uvh \ \

# install the driver (I have an i686 pc, you might need a different architecture, like 64_32 or something similar)
yum install kmod-nvidia xorg-x11-drv-nvidia-libs.i586

# reboot to make changed take effect

This only got me a 1024×768 resolution, though… Which pissed me off…

I started looking around the internet for a way to fix it in the xorg.conf itself, which I’d done on Fedora 9 before, but didn’t remember how (the reason I’m writing this right now), but didn’t actually find what I was looking for.

In the end I found 2 supposed fixes, one added a Modes option to the “Display” section of the “Screen” section, and another was to add a DisplaySize option to the “Monitor” section.
Well, I found out I needed both, so I added DisplaySize 1280 1024 to the “Monitor” section and Modes "1280x1024" to the “Display” subsection of the “Screen” section.

Now it’s working again, running at 1280×1024 with screen compositing (so I can run gnome-do with docky theme, which I’m trying out for a while).