|
If you don't get an answer here try asking in the Workflow MSDN Forum.
Kevin
|
|
|
|
|
Is it really important to create event log sources using the method CreateEventSource of the EventLog class? I tried to write a log to an event source that didn't exist in the "Application" log, and the log was written successfully(without creating the source). If it's possible to write event logs to sources without creating them, why should we ever use CreateEventSource?
|
|
|
|
|
CreateEventSource has two purposes.
The first is if the event log didn't exist. In your case, if the Application log didn't exist, you'd have a difficult time writing to it. You have to create the log first before you can write to it. This, obviously, doesn't apply to the Application log on NT Kernel Windows because it's always created when Windows is installed. But, for custom event logs, you have to create them first before you write to them.
The second is security. Not every application can write to every event log. For example, the Security log is off-limits to your application. You have to be cleared to write to an event log. You also have to have a registered event source on the machine in order to write to an event log. If the event source you're using already exists on the machine, you don't need to to create one. YOu simply specify the existing event source.
If you don't specify a Source, th eonly log you can write to is the Application log, which is available for writes from any application, or I should say that it is available for write from any event Source.
Normally, if you create a custom event log, you'd do this at the time your application is installed, not during the execution of your app. Along with the log, you'd create a new Source that is mapped to that log. When your application is run, it would use this Source to write to the log.
|
|
|
|
|
Hi, I have a problem of converting .flv video to .3gp format automatically on my ASP.NET web site. Unfortunately I was unable to find any managed library I can use to solve this task. Do anybody use some or can point me the page I can find some information on how this can be perfomed? Thanks in advance.
|
|
|
|
|
Not sure if there is any. Have you tried googling it?
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
|
|
|
|
|
Yes, sure. I've tried to find it, the results was not so good. I've found just one managed wrapper for library which supports .flv but it is not possible to convert to .3gp.
|
|
|
|
|
I'm writing a windows service that builds a URL with a specific query string that needs to be sent to the internet. I don't care about the response coming back. How would I do this?
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Actually, in this case the easiest thing to do is probably use the WebClient. It's got several convenience methods for sending requests and since you don't seem to need anything complex (you don't care about cookies or authentication?) it should do the trick.
Also, if you haven't already, take a look at UriBuilder. A very convenient little class that will build full Uri's and query strings for you.
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
|
|
|
|
|
MSDN states the following for the ServiceBase.EventLog Property: "The constructor initializes the EventLog property to an instance with the EventLog.Source and EventLog.Log properties set. The source is the ServiceName of the service, and the log is the computer's Application log. These values are set automatically and cannot be changed for automatic logging of service commands."
Does this mean that the installer class(inheriting from System.Configuration.Install.Installer) associated to the service automatically creates the source for the event log of the service when the service is being installed by the tool installutil.exe? Or should I create this source manually in the installer class(by overriding an appropriate method of those of the System.Configuration.Install.Installer in my derived installer class)?
Appreciating your feedback. Thanks in advance!
|
|
|
|
|
MSK61 wrote: MSDN states the following for the ServiceBase.EventLog Property:
Yes and below that it says:
If you want to write entries to an event log other than the application log, set AutoLog to false, instantiate a new EventLog in the constructor for your service component, and override the OnStart, OnStop, and other command-handling methods to explicitly post entries to that log. You cannot use this EventLog instance to write to logs other than the Application log.
That seems pretty clear to me so I am wondering how you got to the question you asked?
|
|
|
|
|
I have been playing around with this for some time and I can't get an elegant solution. My code always looks like I am missing some obvious library.
We have a lot of old fortran code lying about doing Numerical Simulations. I am trying to get some movement into a sensible coding environment. It is becoming prohibitive using Fortran since the skill set (across our company) is diminishing and therefore becoming expensive.
Step one:
Recompile code using the SilverFrost compiler using the .NET options.
Step two:
Call Fortran code from C#.
Step Three:
Start putting result from Fortran into a biggish Sql say 5GB per model run od so
I have got something sensible for steps 1 and 2 and general movement is going in the write direction, step 3 seem to be convoluted.
say I have 1 dimenesional array of doubles, I simply want to record in the DB
something like
Index,Answer
0,0.1
1,0.2
2,0.3
3,0.4
4,0.5
5,0.6
6,0.7
7,0.9
currently the Fortran just writes CSV files in the above format.
We could bulk copy the CSV files into the DB but seems like an unnessary step (the CSV file), why not direct?.
We could convert the Arrays into DataTables and use SqlBulkCopy,
( just making the DataTable seems inelegant )
We could write a custom IDataReader for arrays and use SqlBulkCopy,
(Idatareaders seems to require an enormous amount of unsued methods to implemnt)
SqlBulkCopy is not an option for things like Access though or SqlCe if we wanted to use a similar methodolgy for smaller localised models
So the question is whats the "best" way of getting a large .net array into SqlCe,SQL and Access datbases.
I guess thats 3 questions one for each format
Carl
DrTip
|
|
|
|
|
You can either do this using an SSIS package (SQL SErver only), or do something closer to this[^], which would be more a more generic approach.
|
|
|
|
|
Thank Dave
I am aware of both of these methods. But I think you have missed the point of the question
The thing we want is to write lots of data to a database directly from memory without first writing to an intermediate text file.
The data is generated from a numerical model that typically takes 18 Hours to run.
Carl
Quick the boss is coming...
|
|
|
|
|
Well, you said it yourself - the FORTRAN code wirte this stuff to a CSV file currently. Your ONLY option is to rewrite the FORTRAN code to NOT write it to a file, but instead open it's own connection to the database and start writing it there itself, as the data is generated, one record at a time. This is because of the lack of a bulk copy in anything other that SQL Server.
modified on Thursday, January 10, 2008 4:23:15 PM
|
|
|
|
|
I was going to ask this in the Vista forum but that appeared to refer more to the Vista win API than to how the .NET framework runs on Vista, so I'm asking here..
Maybe my Google-fu sucks, but I can't seem to find any pointers on how to write applications to ensure they'll run on Vista without elevated privileges.
In particular, I'm interested in the following things that will trigger the elevated permissions system:
* Which P/Invoke functions to avoid
* Which .NET namespaces to avoid (the Cryptography namespace forces elevated privileges?!?!?!?!?!?!)
* Which files and directories to avoid (I know, \Program Files\ and %WINDIR%\system. Any others?)
Also, a bonus would be some kind of tool that will tell me specifically which of these areas will cause Vista to refuse to run my application. I found this tool[^], but all that does is report errors from the low-level operating system API that mean very little to me.
Fundamentally my issue is that I'm writing an application that RUNS fine on XP, INSTALLS fine on Vista using a VS2005 setup project, (but it DOES request elevated permissions), but it will not RUN on Vista (UAC does ask to allow the program to run). And even when the user selects ALLOW, the program still crashes.
For the life of me I can't seem to pinpoint why. The best I seem to be able to find are recommendations of embedding a manifest file to demand admin privileges. Well, that isn't what I want to do. I want my application to run under normal user permissions, but I can't figure out WHAT in my application is triggering the request to elevated privileges.
Pointers are appreciated... this is pretty aggravating.
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
modified on Monday, January 07, 2008 4:03:11 PM
|
|
|
|
|
|
Thanks Mark, I'll take a look. I also found a 30-day eval Vista virtual hard drive, so I will do some testing.
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
|
|
|
|
|
Don't think of what to avoid, think of what the minimum you should do is. It's safe to write to the user's profile. That's pretty much it. Anything that changes the system configuration is likely to fail for a standard/non-elevated user.
No APIs force elevated privileges. UAC will automatically apply elevation if it thinks that you're a legacy setup program (if your program name or resources contain the words 'setup' or 'install') or if there's a compatibility shim detecting the program that requires it to run elevated. Otherwise, your program does not prompt, and runs in a 'virtualized' environment, where writes to certain registry keys and protected disk locations are redirected to shadow folders under the user profile.
A manifest is necessary to tell Windows Vista that you are aware of the presence of UAC. If you never want it to prompt, set the requestedExecutionLevel to asInvoker. This means 'never ask for administrative rights even if the user is an admin'. The other available settings are requireAdministrator, which always prompts (for confirmation for administrators, for admin credentials for non-admins), and highestAvailable, which prompts administrators for confirmation but runs without admin privileges, without prompting, for non-administrators. The latter is a bit of a compromise and you're recommended to strip the administrative functions out into a separate program.
As soon as you install a manifest containing one of these settings, Windows Vista will disable the legacy redirection. You'll then get exceptions as appropriate as you use APIs for which you don't have permission.
Another simple way to test is to run your program under Windows XP as a standard user. That'll blow up all over the place.
The Windows security model is so much more sophisticated than a simple admins can/non-admins can't system. Most of Windows security is based on Access Control Lists, which define exactly what different security principals (users or groups) can or can't do. In addition there are a separate set of privileges which are again assigned to users or groups; these privileges largely allow you to override the ACLs (for example, the ability to change the ACL is normally a permission in the ACL, but the owner of the object can overwrite it even if this permission is denied to them in the ACL; administrators also have the right to Take Ownership of the object, then they can write to the ACL).
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
Mike Dimmick wrote: Another simple way to test is to run your program under Windows XP as a standard user. That'll blow up all over the place.
Did that.. didn't reveal the issues that came up on Vista though.
That said, a manifest both in the installer and in my executable appears to have resolved everything.
Incidentally, the installer (the bootstrapper, actually) needs its requestedExecutionLevel set to requireAdministrator in order for installs for Standard Users to work correctly. I'm not sure why that is - if it is set to asInvoker, when the Standard User goes to use the program for the first time and the installer does the shortened install, the files and folders I create in the user's AppData folder don't get created.
If the original installer uses requireAdministrator, however, that works just fine.
Anyway, thanks for your insight 
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
|
|
|
|
|
I like to use the SerialPort class (namespace System.IO.Ports) in an existing MSVS2003 project (.Net1.1).
Is this possible and how to proceed?
Can anybody give me a hint?
Regards Peter
|
|
|
|
|
Hi, SerialPort is part of .NET since version 2.0, and MSVS2003 only targets .NET 1.1,
so no you can't use it.
You could use MSVS2005 (the Express Editions are freely downloadable) and convert
your project, which typically is straightforward. Major drawback is the target machines
for your app now need .NET 2.0 (which is freely downloadable too, but needs to be installed).
|
|
|
|
|
Thanks for the reaction
Peter
|
|
|
|
|
Hi
My company has been happily bumbling along storing configuration data for our application in the registry and storing any application data in \Program Files\application\data. Unfortunately a Vista laptop has just been presented to me with the request to get one of our applications to work on it.
I think we are going to have to upgrade our data storage policy. Can someone point me at a MS best practice document of what we really should be doing? Or better still something that will work with Mono as well?
Thanks
Dave
|
|
|
|
|
|
Dear all,
I have a question about preserving the backward versioning compatibly in Visual C++ .NET 2003:
I am building a win form control using Visual C++ under Microsoft Visual Studio .NET 2003 framework. I already made a previous release of this control with a version number (1.0.0.0) and I have customers who already built projects using my control. Currently I am working on a new release of this control with a new version number (2.0.0.0) which includes new features and properties (I updated the major and minor version numbers in the assembly file). My issue is that this new release recommend a change in one of the old properties (that existed in version 1.0.0.0) default values, I need to know the correct method of changing the old property default value without affecting the already existed projects that use the old default values. In another words, I need to preserve the backward versioning compatibility.
Please advice..
Thanks in advance..
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
