|
How the code looks depends very much on how you store the information for the users, e.g. what kind of database, the database layout, what data you store, how you communicate with the database, etc.
You use Request.UserHostAddress to get the IP number of the user.
---
b { font-weight: normal; }
|
|
|
|
|
Dear Gufa,
can you send me code for this problem?
regards
pawanmishraji@gmail.com
Pawan Mishra
MCA, MCP.NET, MCAD.NET
|
|
|
|
|
Hi,
Microsoft released this article last week:
http://msdn.microsoft.com/winfx/default.aspx?pull=/library/en-us/dnlong/html/netfx30.asp
In particular:
Deploying .NET Framework 3.0
This section provides information about deploying the .NET Framework 3.0 for use with your applications.
Software Requirements
To install .NET Framework 3.0, you must have one of the following operating systems installed on the target computer:
* Microsoft Windows XP Home or Microsoft Windows XP Home Professional, with Service Pack 2 or later.
* Microsoft Windows Server 2003 family with Service Pack 1 or later.
So they dropped support for Win98 & Win2K and while we don't care about Win98 at our company, we still have lots of clients with Win2K Servers and Workstations. My question basically is whether this bothers others? I can't really understand why technically it wouldn't run on Win2K if it can run on WinXP...
|
|
|
|
|
You really haven't looked at the Win32 API changes between 2000 and XP, have you? Shell improvements?? I could go on, but why?
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
What I was really getting at was that .NET 2 runs on both (XP and Win2K) and .NET 3 is basically all the .NET 2 class libraries and runtime anyway... why drop support for something that worked? Please don't be so arrogant to think that I don't understand that APIs change between OSs. All I'm trying to say is that the difference between .NET 2 and 3 are minimal yet they dropped support for two operating systems, why?
|
|
|
|
|
I think Win98 and Win2k may have moved into their unsupported phase now. And when that happens MS tend to automatically remove them from their target OSes - regardless of whether technically they could support them. That's the impression I get anyway.
Not sure whether Win2k was unsupported when .NET 2 was released but I guess when .NET 2 was in beta it wasn't - hence support for Win2k. However, it's probably not quite as simple as that - more their guess as to how many developers are still on Win2k.
Kevin
|
|
|
|
|
Because Win98 and 2000 are both End-Of-Life as far as Microsoft is concerned. But, yes, all the current classes and stuff would work, but the stuff that .NET 3 adds, like WPF, won't work on 2000.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Dave Kreskowiak wrote: Win98 and 2000 are both End-Of-Life
Don't care about Win98 but  for Windows 2000.
|
|
|
|
|
Ah yes, apart from my post below I just remembered that .NET 3 is just all the WinFX stuff rebranded. This was only ever planned to be available for Vista and WinXP - hence no Win 98 or Win2k, regardless.
Kevin
|
|
|
|
|
Hello,
what is the best code documentation generator for .VS 2005?
Is it NDoc for VS.NET 2005 the best, or you know better alternatives?
Thank you for suggestions
|
|
|
|
|
I have a simple component in COM+ which will pass an object to a client app and then accept it back. All that the client is doing is updating one of the properties in the object. However, when I pass the object back I am getting the fillowing error:
Cannot find the assembly DataStore, Version=1.0.2371.28609, Culture=neutral, PublicKeyToken=c8d286e2247b3c51.
where "DataStore" is the name of the dll which contains the class of the object I am passing around.
I do not understand why it will happily pass the object out of COM+ but then error when it is returned. (Class has been marked with "[Serializable]") Can anyone help at all?
For ref, I have the following binaries:
1) dll in COM+
2) exe on client
3) dll on client which is called by exe and also calls COM+ package
4) dll containing data storage object which resides on Client and COM+ server (although not included in the COM+ package itself).
|
|
|
|
|
Hi,
I'm trying to implement an MS-IME dictionary in C#. According to the documentation here[^], I need to make a method called CreateIImeActiveDictInstance that MS-IME will hunt down and call. Problem is, I can't think of a way to make a global method in C#. I do know that MSIL is capable of global methods. If I can, I want to avoid having to write it in C++.
Any ideas?
Thanks in advance.
|
|
|
|
|
There's no way to do this in C#.
As you say, MSIL supports it, so it would be possible to write a small piece of MSIL that implements the required method. From there, you would need to make a single DLL; either disassembling the C# code with ILDASM then building the disassembled code plus the new MSIL file with ILASM, or if you're targetting .NET 2.0, using Visual C++'s link.exe. See this topic[^] for more.
You could also use a small piece of C++/CLI or Managed C++ code to do this. Again, you'd have to either disassemble/reassemble or use the VC++ 2005 linker.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
|
I tried to install a app that was made a year ago on a new computer with net framework 2.0 installed but when I fired up the app it crashed and demanded that I install net framework 1.1! Is this a bug in the app or do all users of said app have to install dnf1.1 even if they have 2.0 already?
If its a bug, how do I remedy it?
Grateful for any clarification
Ulf Rosvall
|
|
|
|
|
If the app is demanding the .NET Framework 1.1, you'll have to install it. Not every app that was written under 1.1 will work with 2.0. There ARE breaking changes between 1.1 and 2.0.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Do you by that mean that it is possible to write a app under 1.1 that will work
under 2.0 whithout the installation of 1.1?
Could you specify som problematic points? Or point me in the direction of a FAQ or like.
I do have the source for the app in question, if I could modify it so as to not demand the installation of the 1.1 on a machine that allready has 2.0 installed that would be very worthwhile.
Thanks
Ulf
|
|
|
|
|
All you have to do is search MSDN for ".net 1.1 2.0 changes"...here[^].
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hey kids,
I've always been annoyed that Windows won't let you drag the tasks around on the taskbar so I thought I might try to write a small app or service in .Net to do this. I've written plenty of .Net web pages and Winforms apps but to be honest with something like this I'm not that sure how or where to start - for example, I assume I'd have to use the native windows classes but that's about as far as I know. Can the taskbar be accessed from v2 of the framework easily? Is it easy to implement drag and drop when it's outside of a form (ie: on the desktop window)? I'm sure this must be possible to do but I just need a kick-start from a few folks more knowledageable in these sort of things than I am.
Alternatively, if asyone knows of a good app or utility to do this I'd love to hear about it.
TIA for any suggestions etc.
Mike
|
|
|
|
|
Since Windows does not allow you to drag-drop items in the Taskbar (which annoys me too), I assume that there is no API which will allow you to do it. If the API existed, then Windows would have the feature in the first place. (I could be wrong about this.)
:josh:
My WPF Blog[^]
|
|
|
|
|
I think Josh is right. I haven't seen any support in the Shell API to support Drag and Drop in the TaskBar.
Of course, this may change in Vista...
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Greetings
I need to fetch microprocessor specific information (brand, temperature, usage etc.) programmatically. Is it possible while I am using .NET. Any ideas on how to do this.
Soon helpful replies will be appreciated as I have to start this ASAP.
Thanks.
Ali
|
|
|
|
|
Ali I. wrote: brand
CPUID instruction at the assembly language level will give you processor specifics.
Ali I. wrote: temperature
Not 100% sure about this. Maybe reading from the BIOS.
Ali I. wrote: using .NET.
I don't think .NET lets you get to the low level that is required for this. Write a .dll using unmanaged code to get results from CPUID and reading BIOS.
Ali I. wrote: usage
You can look at the PerformanceCounter class for that in .NET.
Hope this is a start for you 
|
|
|
|
|
Per usual it has to be as confusing as possible when it comes to C#.
Something simple in VB like My.Settings.name becomes appnamespace.Properties.Settings.Default.name.
This isn't really that bad except that the word Default is associated with both User and Application settings.
The first time Settings.Default.Save() is executed, which by the way can only affect User settings, my definition of the word default goes out the window. Even though there are lines of code buried in the designer which contain System.Configuration.DefaultSettingValueAttribute, the values associatied with them have nothing to do with the values returned by Settings.Default following a save.
For reasons I have yet been unable to fathom the initial value for all settings is stored both in the designer code and the app.config file. The next thing I should do is change the app.config file manually and see which "default" value is actually returned. No real question this time. Just needed to vent a bit...
>>>-----> MikeO
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
