PlausiblyDamp

Easiest way is just to use SSL rather than plain HTTP - that way all traffic is encrypted. As to your other problem can you ping the server from the client?

If you just wish to transfer information to a remote system then you may want to investigate web-services as a possible means. When you say put the app on another computer do you mean the client, server or both? If you are moving either the client or server make sure you are trying to connect to the server using either it's correct name or ip address.

If you embed the Dlls it will make the whole compile / debug cycle much harder, and also if you bug fix one dll you would have to redeploy the whole lot. Also are the 2 dlls in question ones you have written or 3rd party ones? If third party then you may not have permission to deploy them in this way - only asking because office.dll is the same name as a MS interop dll (and the vbide.dll name rings a bell as well). If you just put the 3 files in one folder then they just need to keep the folder contents together and things should be fine.

Tried it here with a simple class and it worked aas expected, feel free to post / attach your code and I'll have a look.

public Class this[int index] should return an instance of Class - you should have access to all the properties and methods of Class. What properties / methods is it displaying instead?

What version of the framework / VS are you using?

Could you post your code for how you have defined the indexer and the class it returns?

You may need to give the ASPNET account permissions to the directory as well

Do you allow anonymous access via IIS? Also in your web.config what authentication settings are you using?

From within the ASP.Net application itself you should be able to use the user class to find out this info label1.text = user.Identity.Name label2.text = user.IsInRole("DOMAIN\Users")

Result of being bored in a hotel a few nights ago. Fairly rough and ready (only took a few hours and several guiness to throw together) but should handle ID3 v1 tags fine. Supports ID3 v2 tags more or less : Provides property access for the more common tags but should read and write all tags. Text based tags are untested with anything but ASCII content. Error handling may be a bit lacking feel free to PM me with any critical problems and I'll try to find time to fix them ;) Can be used something like MP3TagLibrary.ID3v2Tag test = new MP3TagLibrary.ID3v2Tag(); MessageBox.Show(test.Artist); //should display artist test.Artist= "This will overwrite the real tag - be careful"; test.Update(); //save changes back. Includes a basic user interface to manipulate tags. As per usual code is provided with no guarantees at all. EDIT: this version appears to work better SimpleTagUI.zip

You can't import down to the class level, only the namespace so the 1st line would be invalid. If you have duplicate definitions you could alias a namespace to a shorter version and use that to fully qualify classnames <%@ import Namespace="MyPeople = MyLib.People" %> <%@ import Namespace="System.People" %> 'you could now use MyPeople.Person 'and can always use MyLib.People.Person

You are required to import the namespaces explicitly, this prevents confusion when the same classname occurs in multiple sub namespaces and compilation errors if in future a revised library version may introduce a duplicate classname in a sub namespace.

Something like TimeSpan ts = dtpCompleteDate2.Value-dtpCompleteDate1.Value; MessageBox.Show(ts.Days.ToString()); or Dim ts As TimeSpan ts = dtpCompleteDate2.Value.Subtract(dtpCompleteDate2.Value) MessageBox.Show(ts.Days) should do the trick

How are you refering to the proxy? IIRC the wsdl.exe tool doesn't put the class in a paticular namespace by default, you can specify on with the /n command line switch.

Which is exactly what my code does. It is a simpler form of your code.

If you are changing the text from inside the form itself you could have done either Me.Text = "New text" 'or just Text = "New Text" without having to go through all the type casting.

Rather than using ActiveX (which limits you to clients running IE on windows - and may have problems with the default IE configuration under XP SP2) you may want to investigate some of the ASP.Net controls. This page contains links to several menu controls. There is an open source menu control called skmMenu that is definately worth investigating as well. Example of using it as well.

In the next VS release they are fixing some of the issues with Source Safe but only for compatabilty reasons. There is actually a completely new version control system being included - far more useful for a corporate environment as it supports things like access over HTTP (great for remote users) and the ability to have certain requirements met before code can be checked in (e.g. must have unit tests written, must achieve a certain % code coverage, x amount of peple must have peer reviewed the code and approved it kind of thing).

You may find http://www.systemwebmail.com/ worth a look.

If they aren't installed they should be on the original install media. Also if you are after a modern VS look you should wander over to http://www.divil.co.uk and have a look at his controls.

If you create a filestream and base your streamreader on that you could seek the underlying stream to the correct position and then read from the streamreader.

Easiest way is to use a MemoryStream BinaryFormatter binaryFormatter = new BinaryFormatter( ); byte[] b = new byte[100]; //make correct size MemoryStream ms = new MemoryStream(b); binaryFormatter.Serialize(ms, MyStruct);

IIRC you cannot choose where to add a control into the collection, is there a particular reason the control needs to be inserted in a specific place rather than added to the end? If you wish to be able to access them in a particular order from the GUI then set the control's tabindex property - that should do the trick.

Is the DLL written in C or C++? If C++ then it mangles the names it exports (this is how overloading etc are implemented) Either way you could try using the dumpbin.exe utility on the DLL to make sure the function names are what you are expecting.