Axinterop.wmpLib.dll Works OK In Debug Build - Not OK In Release Build
Feb 15, 2012
I have a Form with a Media Player in it. Which plays a Song.
[Code]...
It's playing in the background since the Form is hidden. When I play itin Debug, everything works fine. When I run the app outside Debug, I get this error: [URL] The Music File is there, but strangely, there comes this weird error.
I am using 2008 Express Edition. I am trying to make a Release build instead of a Debug build.Under Tools->Options, Projects and Solutions->General - I checked Show advanced build configurations. The option to switch configurations does not show up in the IDE.
After this, I went to the Project Properties->Compile and switched the Configuration from Active(Debug) to Release.After building, I looked in my project directory, however only in the Debug sub-directory was the .exe and nothing in the Release sub-directory.I have used Visual C++ Express Edition, where I noticed that if you do not change to Release in the IDE than after changing to Release in properties, resets the project to the last configuration setting which is usually Debug.how to make the Debug/Release box available in the IDE, since Tools/Options does not make it show up?
I have some very simple questions about making a release build exe in vb.net using MS VB 2010 Express.
I realize that my project's executable is built in the bin/debug folder. However, when I copy this to any other location on my computer or someone else's, this executable does not function. I have read that I need to create a release build but in MS VB 2010 Express, when I use the Project-Properties menu and change the Compile tab configuration to Release and the path to binRelease, I still get the exe in the binDebug folder and not the binRelease folder.
1) Is it normal that exe's from the debug folder do not function outside of the debug folder?
2) Most importantly, if the release build produces a faster exe, could someone please explain step by step how to do this with MS VB 2010 Express ? I do not see any button on the compile tab in the project properties that actually builds the release.
I was able to build both debug and release versions of my VB code before now I no longer have the option to build a release version. How do I turn it back on
So when i build or click debug on my program. No errors come up and its smooth. So i decide to publish my programme. However. I come up with a bunch of errors during the publishing.
Here they are:Error 1 Cannot publish because a project failed to build. 1 1 Simple CALC
Error 2 Unable to copy file "binReleaseSimple CALC.exe.manifest" to "binReleaseapp.publishApplication FilesSimple CALC_1_0_0_0Simple CALC.exe.manifest". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
I am developing an application using Visual Basic .NET 2005. The application works fine in the PC which Im using to develop it. I make the setup.exe I install the application in other PC and the application doesnt work but it I replace the app.exe with the one in my debug folder it will work.
I wrote a little (like 40 lines little) Winforms application with VB.net in Visual Studio 2010. Now I've released the code as a Google Code project. It's easy for a developer to get the source but I'd like to make it easy to install too.
What I did was make a release build then zip up what it created, this included a setup.exe. There was also an option to "publish" my project which looks like it can enable update checks and other stuff.
I am having another issue with WMP in VB.NET 2010.I wrote an app using WMP in VB.NET 2010, using .NET Framework 4.0 of course, but had to change the framework target to 3.5. After doing this, the WMP component does not work. How, if I even can, fix this problem so that the program will run on .NET Framework 3.5? The error says that it could not load AxInterop.WMPLib.dll because it was built in a runtime newer than the currently loaded one.
I have a dll library that I built to help reduce the amount of boilerplate code copied over from project to project. There is a timer running in the dll to maintain the connection to our machinery via RPC. When I debug my project and break the RPC connection my code gracefully tosses a disconnect event from the dll library and my main form catches the event and handles it appropriately.Now, build for release. When I break the RPC connection a unhandled exception is tossed from the library that apparently is not caught elsewhere.
The weird part is that the code that is throwing the exception is in the timer and the calls are all wrapped in try/catch blocks and the catch block swallows the exception and does other cleanup work.I don't get how in debug mode everything is fine but in release it is not. That part doesn't make sense to me. I tried looking at the exception object and setting a handled property on it but it's not available. Is this normal behavior what I am seeing?
I just recently started utilizing numerous libraries in my projects to keep my solutions more trimmed and easy to follow. Hopefully this isn't a problem with libraries I had not considered.
I have a form and I drag and drop a control in VB.NET. I have a line say, private WithEvents radioButton RadioButton
Also, I have a handler like, private void click(.....) Handles radioButton.Click { ... }
Now, When I build this is .NET 3.5 in release mode, and see the generated code in reflector tool, the code is something like: Private Overridable Property radioButton As RadioButton . . . <AccessedThroughProperty("radioButton")> _ Private _radioButton As RadioButton And how do I avoid the generation of new properties and fields?
I've searched the VS settings and haven't discovered why the bin.Release folder is empty after a build. The bin.Debug folder output is normal. The same occurs with the obj.* folder.
Every time I compile a new release build in vb.net 2009, the file version number of my main exe is correct, but the assembly version number is the same as the last build instead of the current version even though I manually change the file and assembly version in the design studio to be the same prior to compiling.The only way I can get the assembly version to be correct is to close Visual Studio and delete the obj folder. Then if I open the solution and recompile, all is well.
Here is the information copied from the About box in VS:
Microsoft Visual Studio 2008 Version 9.0.30729.1 SP Microsoft .NET Framework
I am trying to build a class that works with a form, but I keep getting the dreaded "Object reference not set to an instance of an object" Error.The form basically collects test grades and assigns them to a collection.My class code is as follows:
Public Class Scores Private colScoreCollection As New Collection Public mintSum As Integer Public mdecAverage As Decimal Public mintMinimum As Integer
[Code]...
I had a similar project I was working on that had a collection in it, but now that one is giving me the same error. It there something with my version of Visual Studio that is causing this error possibly?
I have a setup project which is full of VB Libraries / apps...when I try to build it in the debug configuration it always errors out with this error[code]...
For the last half an hour, whatever changes I make in my app, when I hit the green arrow to start debugging nothing changes. The app seems to be running from a previous build?There's no error/warnings/messages on build.
I have a relatively small app that Im building using vb.net 2.0, and nant. Its a app that calls out to an external exe to produce some output files, then processes those output files afterwards.I have built an interface to the exe, which I have created a stub implementation and the real implementation, what I would like to be able to do is use nant to either create a DEBUG build of the app, which calls the stub implementation, or create a PROD build of the app which will use the correct implementation.
We have a couple of DLLs that need to be put in the GAC at compile time only in Debug mode as this is what developers use locally. Release mode will be the Continuous Integration server build and we will not want to put any dlls in the GAC. We used to do something similar with post build events on a project, but if a post build event can be conditionally run if debug. What is the best way to achieve this?
From my DLL project I have succeded in making AutoCAD launch by pressing F5 from VB.net IDE (Visual Studio 2008) en route to try to make debugging of the DLL easier ...
... however one last obstacle is currently in the way and the obstacle is that for some reason when I hit F5 and AutoCAD is launched my breakpoints are not recognized at all... and program runs from start to finish instead of allowing me to debug ...
It issues a strange message which says "The following module was built either with optimizations enabled or without debug information... to debug this module, change its project build configuration to Debug mode..." and it is all weird because as far as I know I am not in release mode .. but in debug mode (anyhow I am relatively new to Visual Studio .NET so I am thinking that my impression could be that I am in debug mode when in actuality I maybe in release mode)...
Here is why I think I am debug mode ...
1. From Solution explorer ... when I click on the Solution Name and view its properties ... the Active config property says Debug|Any CPU
2. When I look at the properties of the project and look at the compile tab it says that the Configuration is Active (Debug) and under Platform it says Active (Any CPU).
3. Under the Advanced Compile Options of Compile Tab from project properties ... Enable optimizations is UNchecked ...
Anyhow with all the settings mentioned above it seems that I have everything okay but then the message above proves otherwise ... and so at this point I know that I am still missing something ... like a setting somewhere... wondering what else do you think am I still missing?
As additional info...there are seven projects in the solution and it is the main one (the one that I set as startup project) whose properties I refer to in all the paragraphs above.
I have more than one file under project. Where do I configure the first/start file when debug? Example: form1.vb is load by default when debug. Now I want it to load login.vb instead.
A particular VB.NET project is actually throwing 'Build Failed' But when I try rebuilding again it says 'Rebuild Succeeded'. It keeps alternating this behavior. Kind of random. Any vbc.exe issue of long locking the PDB or xml files?
I have a vb.net 2008 windows form application that I was just assigned to work on. how to maintain and test changes to both the pre build and the post build events? Can you tell me how to test these events? My postbuild event, I believe calls a project file in the solution file that wraps files together in a bundle in debug mode. Can you tell me how the posbuild event works and when it is called?
I just created a simple application. I Builded that using build->build myapp. I got .exe of that application. i runned. all went fine. but when i closed that app, even after closing it is in memory. it is still running. how to deploy it properly?
I am confused about the folders that setup creates. What are Debug, Relese and Bin folders and what folder I need to give to my user while distributing the application.
When an error occurs in any of my .NET assemblies the user just gets a generic error saying "MyApp has encountered a problem and needs to close. We are sorry for the inconvenience." I would like the user to to see the error message and line number if possible.From what I understand you need to deploy the pdb file along with your assembly. I did that, but it had no effect. This is a Windows application.
If I have Debug.WriteLine method in my code, do I need to comment all these methods before producing the Release version? Or does the compiler just ignore them?