How to make my program run at startup using installsheild - vb.net

I was wondering how can I my program to run at windows start-up using the registry editor in installsheild limited edition in visual studio 2012. The program is a timer for individual users and for it work properly it needs to e able to run automatically at startup. it's written in vb.net, incase it's important.
I did see a similar question which point that i can do it using the following line:
My.Computer.Registry.LocalMachine.OpenSubKey("SOFTWARE\Microsoft\Windows\CurrentVersion\Run", True).SetValue(Application.ProductName, Application.ExecutablePath)
but i was wondering how to do it using the installsheild.

Related

How do I make my VB.NET program run in MS DOS environment?

So if I made a VB.NET normal windows.form application and then booted into ms dos mode, i am able to run notepad and taskmgr but any normal exe file will just give me an error saying it can't be run in MS DOS mode. Is there a way I can make it compatible with MS DOS environment?
If by "MS-DOS " you mean "command Line" then you can mark your Project as a "Console Application" when you create it in visual studio. This should enable it to run in the command line.
If by "MS-DOS" you mean the 20 year old operating system by Microsoft, it cant be done.

How do I create a package of my application in VB.net which can run on other's systems too?

I made an application in Visual Studio 2012 using VB.net language.
I want to make a package or a setup so that any user whether they have visual studios or not can run my application.
I searched on internet and what I found is that there is something like statically or dynamically linking. Do these relate to my question?
Please give me a step by step method of packaging so that my application can run on Windows without needing Visual Studio or any other program to run it.
You will find it in the menu under Build -> Publish.
This will produce an executable that can be run without Visual Studio. The .NET Framework has to be installed on the computer though, but that usually is.

Getting a .dep file to work on Windows server 2008 R2

I am working on a dashboard related project using the MS BI stack integrated with SharePoint. I have a configured POC server running on Windows Server 2008 R2, SQL 2012 and SharePoint 2010. I am trying to run one of the MS tutorials that I have already completed on the MS virtual labs in a completely 2008 environment but doing so within my SQL 2012 / SharePoint 2010 environment and this requires I use the .dep file to set the tutorial up. When I first tried to run it I got the windows doesn't know which program to run it with but since the server is in a sandboxed area without net access it cannot search the web for the correct program. In the tutorial it mentioned the file ran via the command prompt so I tried opening it with that and unfortunately nothing happened, but I forgot to untick the always associate box so basically I now have two issues.
First is getting the .dep file back to having no default associated program to run with or finding out what actually is the correct one and the second is to actually get the required files I need to run the .dep file and set-up the environment for the tutorial. Unfortunately MS does not have a nicely detailed list on this.
I have tried using GPMC.MMC to remove the file association but as it is connected to our active directory the default features do not match up with what the technet article states on doing this and I don't want to cause errors on our active directory. Any advice on how to get this working would be appreciated.
You can try downloading the offline training kit.
This training kit should contain a folder with the name "assets". Into this folder you can find an installation of the software "DependencyChecker.msi". Just do this installation. The installation associates the .dep files with the "Dependency Checker Tool"
Secondarily, you can google around to find "How to install the Microsoft Dependency Checker Tool".
In the next link Microsoft talks about the tool.
http://msdn.microsoft.com/en-us/identitytrainingcourse_silverligthandidentity2010.aspx

Class running when I open VS 2012

I'm working on Visual Studio 2012, on a .NET project.
I have a class that pops up a window asking the user for input. The window isn't set to show up at start-up.
Whenever I load my project, before I even build it, that class starts shows up.
When I run my program using the exe file, I don't have the same problem.
Does anybody know how I can prevent it from happening?
Thanks

Running .EXE file made in visual studio 2005 failure

I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.