I know this isn't straight programming and debated posting this for a few days. I am interesting in writing a utility to talk to network switches and gather statistics via CIM. After several days of searching I can't find any decent examples to help get started. I did find one project from Microsoft but it queries machines running Windows and requires Windows 8. I have Windows 7. Also, the few examples I've seen use the WMI which I think is for talking to other Windows systems.
Does anyone have any suggestions for examples or other reading?
I found a project that I think will work. If anybody else is interested, look into wbem-sharp.
I'm not sure how active wbem-sharp currently is...
As an alternatve, you could use the SFCC client, and integrate its C-Language client API into C#. SFCC is well-maintained and supports the current CIM/WBEM standards.
Related
There are various questions (mainly around 2009 to early 2010) discussing use of the Mono framework to write apps in C# and deploy them to iPhone. Also there is some discussion of the Unity Framework, but I'm more interested in a fairly standard UI app.
Has anyone successfully developed and released a commercial quality app using C#/Mono? If so, what were the lessons learnt? Pain points? If you know of other people who have done so, how have they fared?
Thanks!
Mark
The basic answer is yes, there are a lot of applications out there that have been developed using MonoTouch. You can find some nice numbers on Novell's site but there are a ton of games and other application is the AppStore that were developed using MonoTouch.
I would start your investigation by going to review articles that walk through the good and bad of MonoTouch. For example, here is a good starting place:
http://www.bryanthankins.com/techblog/2010/01/17/monotouch-review-porting-an-obj-c-app/
http://www.devproconnections.com/article/mobile-development/review-monotouch-enterprise
Then I would look through some tutorials to see how exactly this is done so you can see if it will fit in your environment. There are a lot out there that show off how to use MonoTouch, including these:
http://vimeo.com/6689472
http://blog.keen-edge.com/category/monotouch/
Finally, I would look at what is happening currently with Attachmate and the takeover of Novell. There are some real issues there that may cause you to reconsider going with MonoTouch. For example, while Mono's future may be unclear at Attachmate, it seems that it might be continued through another company:
http://ostatic.com/blog/mono-continues-without-novell-attachmate
This uncertainty might not be what you want in a project you are counting on so you need to work through that before committing.
Your sdk rocks. I have built several apps using the sdk quickly, so thank you for that.
I have searched this topic, but could not find a direct answer.
I will try to explain it as clear as I can.
Like many other developers, I am hosting on our server more than one app.
I have managed to make apps work both from web.config and by passing IFacebookApplication to FacebookContext.SetApplication().
As it was mentioned on other posts, setting the configuration programmatically via FacebookContext.SetApplication() seems to be the only choice for me now.
The BIG questions:
Is this method setting the
IFacebookApplication for the entire asp.net application? I mean,
is this change global? Or is it just
for the current FacebookClient?
if I have a high user concurrency on
different fb-apps(on the same
asp.net application), will calling
FacebookContext.SetApplication() *simultaneously* from each fb-app make errors/collisions?
Is it "concurrency safe"?
I will appreciate concrete and direct answers.
Thank you for your great work!
Cheers,
-Itye
I am a complete newbie to SNMP. Recently, I am trying to write a simple program that is supposed to monitor and modify a data file in a remote machine. The file itself could just be a plain-text file or whatsoever. I was introduced to the SNMP, and tried to figure out a way to make SNMP do the job in Windows OS. The prefered language is C# or any .net. I have been googling for a few days, however, did not find a good how-to instruction to do so.
Really need help on this to get my job done.
Thank you very much,
Terry
Here's one SnmpSharpNet. More can be found here.
I use SharpSnmpLib. It works very well for SNMPv2 and is pretty easy to understand
I'm trying to figure out how to access the calendar of Exchange 2003 from a remotely hosted ASP.NET/C# page (I only need to read and display calendar appointments/meetings etc.). As I understand it, I'm mainly down to two options - using WebDAV or the Exchange SDK.
I have found some good examples of how to use WebDAV, although I've not yet gotten it to work properly. I haven't looked too close at the SDK yet, and before I spend time on that, I'm wondering if anyone's got any pros and cons with the two different techniques, and any suggestions on which I should go for?
Any useful SDK links would also be greatly appreciated!
As you say there are a number of ways to do this, but webdav is the best bet, as it is supported by MS from managed code where as CDO tend to have greyer shades of support depending on what you are doing.
If you are new to webdav it may be an idea a looking at some of the wrapper classes around as that could speed your dev up. I have used a 3rd party one
http://www.independentsoft.de/webdavex/index.html their support is lighting fast !
The MSDN documentation is probally the starting point
http://msdn.microsoft.com/en-us/library/aa143161(EXCHG.65).aspx
here are others that i have had booked marked before show examples
http://msdn.microsoft.com/en-us/library/aa123570.aspx
http://www.msexchange.org/articles/Access-Exchange-2000-2003-Mailbox-WebDAV.html
http://blogs.technet.com/kclemson/archive/2004/01/23/62247.aspx
http://blog.mbcharbonneau.com/2006/10/26/using-net-and-webdav-to-access-an-exchange-server/
My company has an existing established WinForm application which in running on WinXP. The application does alot of sound processing using DirectSound.
My company would like to evaluate Mono, as an alternative on a per workstation cost to Vista/Win Server 2008.
I've heard that different estimates, ranging from 'it will work easily on Mono' to 'it could take months of recoding in certain cases to get a WinForm app to run with Mono on Linux'.
Does anyone have a good real world experience with this?
A good link reference?
I would like to get a better idea before I commit to testing.
Thanks!
The WinForms part will be easy, you may have to do very little as Mono now claims to support Winforms 100%, however all the DirectSound calls will have to be rewritten to use an API available on Linux, ALSA being the obvious choice.
I have written small apps in VS 2005 and ported them with ease to Mono. If you do a lot of P/Invokes, then you'll have to take that into account, as those may have to be completely rewritten or rethought.
Also, check out MOMA: "The Mono Migration Analyzer (MoMA) tool helps you identify issues you may have when porting your .Net application to Mono. It helps pinpoint platform specific calls (P/Invoke) and areas that are not yet supported by the Mono project."
Mono can help you move the managed code, but it will not help you move the audio layer.
Sadly, the .NET framework does not provide a comprehensive API for audio processing. It merely provides a way of playing back a small sound sample, and it is not even very good at this (See Jeroen's post about audio gaps when running the C64 emulator under IKVM).
You will have to research which Linux API maps best to what your audio application is doing.
Lennart Poettering blog entry on audio is an excellent starting point:
http://0pointer.de/blog/projects/guide-to-sound-apis.html
Once you decide on an API, just like in Windows, you will have to P/Invoke the API that is right for you.