I got that because that is what you said. Since you're new here I guess you don't understand the "Quote Selected Text" button and didn't see the "bynagari wrote:" text.
There is no way to do what you are asking. SoundPlayer requires either a path to the file or a stream. If the blob is in the database it obviously isn't a physical resource with a valid path. Neither is it a stream. Unless, as I said, SQL Server FILESTREAM will work for this.
I don't know if this will allow streaming, with pausing, though.
The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.
- John Carmack
I created a form that has an event handler that binds the data to the form at load time, it works perfectly until I add a GroupBox. Once I added the group box, the Form Load event is not firing. I see that VS is still adding the load event.
Not sure what is going on, partly because you only showed a very small part of your code; my guess would be you have now moved your data receiving controls into a groupbox however you did not move your classmatesBindingNavigator.
However, unless your form's constructor throws an uncaught exception, I know of no way to not get a Load event. Are you sure you observed correctly?
Thank you for the reply. Yes this is exactly what I did. I've moved the data receiving controls into a new groupbox. I'm trying to learn how this works. I don't know how or where to move the classmatesBindingNavigator.
I checked BindingNavigator, I now don't think it matters where it sits.
I'm still not convinced about your Load event not firing. Is the event still wired? (does it show a handler in the properties pane? or do you still see the "Load += new EventHandler(...)" bit in the designer file?
Try putting a breakpoint high up in the event handler; alternatively insert a MessageBox.Show().
Yes, the event is showing in the properties window under "Load", and I do see it wired in. When I set a break point at the entry to the event, I can see that it never hits, the form loads and we never hit the break point.
If I comment out the two GroupBoxes above and change nothing else, rerun the application with the debugger, I stop at the Load Event.
I thought I lost my mind at first, wondering how the load event is not hitting when the form is getting loaded.
I tried creating a simple Hello World form, placed a GroupBox on the form, added a label within the GroupBox, added a MessageBox.Show to the Load Event and it works.
So I then added a MessageBox.Show to my Class Reunion application and it doesn't give me a message box.
Here is the code that setups the form. I eliminated the code for the controls.
I think you are also right on moving the bindingNavigator because if I call the Load Event, the bindingNavigator shows I have 433 records, when I click the next record button, I do not see any data in the controls.
I have developped an Add-In for Office Word using Visual Studio 2008 and VSTO.
At some point, as I save an XmlDocument, IsolatedStorage is invloved.
For this particular kind of save, my Application Domain must be correctly set up.
I am having real trouble finding an article which explains what the relationship is between the various versions of C# and the .NET (and ASP.NET) libraries. I want to be able to answer questions such as: if you want to use, say, C# 4.0, does that tie you to a minimum version of .NET (and the CLR)?
Tricky to answer that one. In principle, C# is just a compiler, which compiles code to the CIL (or MSIL). Now MSIL has not changed greatly since standardisation (I don't even think it has changed), so things look bright there. The problems are that:
C# is not a pure compiler. For some language features (for example it's basic object implementation), it relies on the CLR to supply the implementation. So constructs which are added to the language may well rely on specific features of the libraries.
Also when compiling code (which happens in asp.net pages), the compilation will rely on System.CodeDom.Compiler to emit the MSIL. Since System.CodeDom.compiler is part of the CLR, you could say that there is a dependency on the libraries ( I'm pretty sure that when you compile through the C# compiler, the compiler relies on the CLR to emit it's bytecode, and will choose the adequate version of the CLR for it's task.
SO: I'm not sure, this is educated guesswork. Haven't found anything on this subject really.
Anybody can offer some more insight?
Technically, there are no different versions of C#; there are only different versions of the framework, which instruct the IDE, compiler, linker and other tools as to what is correct and what is not. If you use the 4.0 framework, then you are automatically using C# 4.0; if you use the 1.1 framework, then you are using C# 1.1.
Because of this, there is no minimum version of the framework, there is only the version needed by your application. If you compile your app to the 4.0 framework, your user will need to have the 4.0 framework. This is because the code does not reference System.Core, it references System.Core version 22.214.171.124 public key token whatever. If that assembly is not found, your user will not be able to run the app. Likewise, you cannot compile your app to the 2.0 framework and expect it to work if the user has only 3.5 or 4.0.
Likewise, you cannot compile your app to the 2.0 framework and expect it to work if the user has only 3.5 or 4.0.
Not entirely true. .Net framework 3.5 and 4.0 are technically extensions of the 2.0 Framework, though dependant on enhancements made in service pack 1 of 2.0. Therefore anyone with 3.5 or 4.0 installed DOES have 2.0 installed, so 2.0 apps will continue to work fine. However you you will have to build against service pack 1 which only comes as part of the 3.5 and 4.0 bundles. It is not available separately, so you may as well build against the later frameworks even if you do not use their functionality.
3.5 to 4.0 is I believe a breaking change, and likewise 1.0 to 1.1 to 2.0. As far as I am aware only the 2.0 Framework has persisted upstream.