PlausiblyDamp

NAnt may be worth a look in this case, it allows you to configure an automated build process via XML configuration files.

Pointers are still supported in .Net but only as a means of interop with other non-managed languages. Within .Net variables that are classes are passed by reference (equivalent of a type safe pointer), structs are a value type and passed as a copy of the data. As a consequence there is no real need to use pointers (and the associated pointer arithmetic) in most .Net based programs. ref (or ByRef in VB) allows you to pass a reference to a variable which behaves like a pointer in most scenarios (but without the associated lack of type safety) - however I would also suggest either searching these forums or MSDN for a bit more detail as it isn't quite as obvious as it first seems.

FxCop is included as well.

In that case what does the variable searchPart contain when the error occurs?

But what was the value of NameS? If you step through the debugger and put a watch on NameS what value does it contain? Also which line is causing the error to occur?

In the line what is the value of NameS? Also you may want to replace CType(NameS, String) with NameS.ToString()

Although not in the current Beta of VS the new Team System is something you will definately like - integrated unit tests and code coverage, plus the ability to set policies on source code check ins i.e. can only check code in if peer reviewed, or percentage of unit tests are passed (providing adequate code coverage is met) etc. Makes source safe look like, well source safe really rather than a decent code control solution.

If you feel a post is offensive, abusive or down right insulting then please use the option to report the post to a moderator (can't remember what the links called). Although as moderators and admins we do our best to identify problem posts some will slip through, if you bring these posts to our attention then we can deal with them (and the poster if need be) much quicker. Please don't let one or two individuals attitudes dissuade you from posting here - we would much prefer to have members who can post in a rational and level headed manner and as such improve the forum's image to potential members in preference to overly opinionated and rude members (regardless of their technical knowledge).

Too be honest there is probably no real reason to inherit from ApplicationException - I believe the original idea was user exceptions derived from ApplicationException where as Framework errors would inherit from System.Exception. then again MS didn't follow this themselves either ;) Some of the FCL exceptions derive from Exception some from System.Exception and some from ApplicationException.

If you are using Framework 1.1 (VS.Net 2003) then there is a FolderBrowserDialog control on the toolbox.

Problem is a define isn't a function but a literal text substitution, one of the arguments would have the ++ operator invoked twice the other once. #define max (a,b) (((a)>(b))?(a):(b)) k= max(i++,j++) ; //above expands to k = (((i++)>(j++))?(i++):(j++)) //spot the error?

You could investigate UDDI ,http://www.microsoft.com/uddi being a good place to start. Window Server 2003 ships with a UDDI service that may make your life easier. In theory :) the clients would be coded to query the UDDI server for the location of the web service - if the service moves then the UDDI server would be updated. As long as the UDDI server's URL doesn't change then things should be reasonably simple.

The main index alone runs to over 160K of text and images (no avatars to slow that down), that has got to be an issue for dialup users however you look at it. Basic maths says that it would take 20+ seconds (assuming full 100% speed on a 56K modem) to download the index page. Lite w/ Blue was the only style I ever used before the migration - simple, fast and did the job.

Language choice seems to have almost religious significance amongst some people and nothing (at all, ever, even if they lived to be a thousand) will shake their preconceptions of a language. Initial in the days of VB1 and 2 it was a simple language that was lacking in a lot of ways, but still gave a reasonable way to throw a GUI app together. VB3 introduced data access and quickly became a popular choice for RAD development of simple data driven apps, but couldn't really compete with a language like C/C++. Then VB4 (shudder). VB 5 and 6 introduced some basic OO concepts and allowed (with maybe more effort than a more powerful language) large scale, enterprise applications to be developed. The main problem was COM introduced a lot of complications (limited OO, reference counting etc). Other languages like Delphi, C++ could wear a COM interface for interop but rarely used it internally - VB was stuck with COM throughout. With VB.Net the choice has become a lot more academic - inheritace, interface, exception handling, threading, memory management are consistent between all .Net languages (as well as the majority of OO languages) and few people would say C# is 'nearly a proper programming language', yet VB has almost exactly the same feature set (plus one or two things C# doesn't). The next release introduces some of the C# features to the VB language (the using statement when dealing with IDisposable for example). Everyone knows the framework was written in C# so that's the best language. In fact parts of the BCL are coded in VB.Net (I have this on authority from 2 project managers from the VB team) and some of the nicer features in the next release (the My object) are coded in VB as well. This misconception of VB's position is something the VB.Net team are aware of and are actively seeking to dispel some of the myths. Certain points have been raised with them (i.e. better samples, more samples in VB, more MS articles using VB rather than nearly all being C#, possible depreciation of legacy VB features like CInt etc) and they just need to prioritise which can be actioned in the next 6 - 12 months short term and then in subsequent releases for the more long term approach. Without being too much of a zealot myself :) Delphi is a powerful language - it's just not one I've had any call to use or develop in, so my experience is limited (but it did impress me, but the pascal based systax is something I've disliked since college). I don't consider myself to be either a VB or a C# developer but a .Net developer anyway. The next generation of the framework adds support for things like Generics to make both C# and VB.Net even more of a competitor to Delphi etc. Just my 2p worth there.

You should be able to use code similar to that posted in this thread within the dll to access the resource.

In C# they deliberately didn't allow #define macros on the grounds that they are not typesafe and can introduce subtle errors that way. Also they can have unexpected side effects for the un-wary - classic example being #define max (a,b) (((a)>(b))?(a):(b)) int i=1,j=2; int k = max(i++,j++) //what's the value of i,j,k now ?

Ignore the actual websites - it's just the devices your need to look at. http://www.cluboverclocker.com/reviews/drives/hard_drives/seagate_usb/ http://www.tigerdirect.com/applications/Category/category_slc.asp?CatId=136

You can only use the validator controls in web applications, not windows based ones. Windows apps have a control called ErrorProvider as a way to indicate errors but nothing with built in functionality :( However, point your browser over here for something that may help.

Could you not include the .bmp as an embedded resource in the DLL?

You could combine them into a single class that is marked Serializable and then send that class over the network.

http://www.knowdotnet.com/articles/kdngrid.html

I suppose that's the point of a dynamic assembly - there is no code persisted only enough of the manifest to allow the LoadFile to work. Been having a look at this on and off all day and I just can't figure out why it won't work as your code stands. It just doesn't seem to emit the type when you do the save. Strange thin gis calling .GetTypes() on the myAsmBuilder will return an array of 1 type, calling the same on m_Assembly doesn't. It feels there should be an easier way to go from an AssemblyBuilder to an assembly rather than having to try and reload it.

You will also need to add a reference to the adox COM dll. Right click references, add, select the com tab and it should be there somewhere.

If you select the web reference in Solution Explorer and look at the property window there should be an option 'URL Behaviour' (or similar) - change that from static to dynamic and it will move the url to the .config file.

If you want a bit more of a challenge have a look at Terrarium, code creatures (or plants) in a .Net language and unleash them into an unsuspecting world...