I finally can't resist a quick rant about VS Express...
I'm currently in the process of designing a fairly complicated website and as part of this it became necessary that I develop a custom ASP.NET Server Control as a component to be used by a couple pages within the site. Now, I read my way through a few tutorials about this (including some of the MSDN docs), and concluding it was simple enough I created a simple class inheriting from WebControl and specifying the ToolboxData attribute, but soon ran into problems. It seems that another annoying limitation of the Express editions of Visual Studio is that you can't develop a website and an associated library (a control library in this case) side by side, since Visual Web Developer locks the DLL file when running its web server. This of course means you can't build any referenced library while the web server is running. Okay, so this by itself is expected (albeit irritating) behaviour and there's probably little anyone could do about it - but then I thought that I would at least be able to build the referenced library once I'd stopped the web server. To my regret I found that Visual WD maintains the lock on the referenced DLL, forcing me to completely close off the IDE before I can rebuild the helper library (in VB.NET or VC# Express), and then reload the IDE and restart the webserver before I can continue testing! Well I think you see the point by now...
I've always been quite pleased since Microsoft made available their main programming languages to those of us (mainly students) who can't afford the paid editions or aren't inclined to get it over BitTorrent. However, I am surely starting to lament the absence of a .NET IDE that can handle multiple language/project types...
Showing posts with label visual studio. Show all posts
Showing posts with label visual studio. Show all posts
Monday, 5 November 2007
Saturday, 29 September 2007
WiX
It's been a long time since my last post, and if I've any excuse it's being busy with several of my projects (among other things), about which I hope to make some blog posts soon, but for the moment I have a bit of promoting to do for WiX. If you haven't come across it before, it stands for Windows Installer XML and is a toolset for creating Windows Installer packages (probably best known to you in the context of MSI setups) from XML source. It's an official Microsoft product but it's hosted on SourceForge, so it's open source and has dedicated developer base. In the past I've experimented with Inno Setup before and I know many developers use this tool or other popular ones like Nullsoft to create their setup packages. Despite their advantages of being well supported and simple to use programs to create installers, I've found WiX has a lot to offer. Here's a few of the reasons I've switched over:
This is just a brief outline of what WiX can do. I strongly recommend you head over to the site, download the toolset (v2.0 is probably best for now, considering it's the most stable and the tutorial is written specifically for it). You can find the tutorial here, but also as a link on the page along with the official documentation. I'm still a total beginner at WiX myself - reading the tutorial, experimenting with a few of its more simple features, and looking at some interesting blog posts about it - but I can already undoubtedly say it's a good move away from the typical unreliable setup.exe installers that have plagued Windows users in the past.
- WiX takes a declarative approach to installing packages on a system, rather than the traditional imperative approach taken by most installer systems on Windows. This basically means that instead of telling the system what to do in a step-by-step fashion, it tells it what state the system should end up in after installation: this includes files, shortcuts, registry entries, and all the other possible tasks you might want your installer to perform. The sorts of problems like unused files and shortcuts remaining on the user's system become virtually non-existent when taking this approach. As soon as you start learning WiX, you'll also soon see why XML is the perfect language for this. Admittedly, it is a slight downside that you have to write your installer source by hand, but a huge advantage is its powerful integrated build support. (I'm just using Powershell scripts to build the installer, but as a friend suggested you could take it the whole way and integrate it with the MSBuild XML files if you're using Visual Studio). Even so, the XML format is surprisingly simple and there are detailed schemas to help write the code accurately. If you still prefer to develop installers by GUI (although I'd probably recommend against it as it may limit you in some ways and hide the true versatility of WiX), there's a few GUI interfaces currently being developed.
- Developers of the installer can independently write their own WXS source files, and then compile and link them without any moving around of XML code.
- Great support for localisation/custom languages, as far as I can see - though I must admit I've only read sections about it and not actually tested it out yet.
- I was amazed to read that the entire installer for MS Office 2007 was created using WiX - there really shouldn't be any reason to doubt its power!
- If you need more convincing, try reading the tutorial (it assumes you're a complete beginner, and probably explains some of the points here better than me) or even glancing at the manual.
This is just a brief outline of what WiX can do. I strongly recommend you head over to the site, download the toolset (v2.0 is probably best for now, considering it's the most stable and the tutorial is written specifically for it). You can find the tutorial here, but also as a link on the page along with the official documentation. I'm still a total beginner at WiX myself - reading the tutorial, experimenting with a few of its more simple features, and looking at some interesting blog posts about it - but I can already undoubtedly say it's a good move away from the typical unreliable setup.exe installers that have plagued Windows users in the past.
Monday, 6 August 2007
Visual Studio 2008
I have recently installed the beta 2 releases of both VB.NET & VC#.NET 2008, and hoping to experiment with some of the more interesting to features like WPF and LINQ syntax, I found that I there were no templates installed at all. In fact, because of this, I cannot even create a blank project. The best I can do is create blank files in Windows Explorer and edit them, or upgrade existing projects. Now, of course I'm considering this a problem with my personal installation, but considering that I have a nice working copy of Vista installed (ignoring all its many usual problems, but remembering that VS.NET 2008 ought to be built for Vista) and that the Visual Studio Express MSI installers ran cleanly, I havne't been to impressed so far. I will keep investigating and post any solution I find here for others who may be experiencing the same/similar problems. To conclude: is this yet another reason to ditch development on Windows and move to Linux, where it's becoming almost as easy to develop in C# anyway? Anyway, perhaps you can look forward to some of my .NET projects being ported to Linux some time soon, especially Messenger.NET, which I'll be looking to bind to telepathy (most likely with telepath-sharp).
Subscribe to:
Posts (Atom)