I have an already created project with plenty of WinForms and specified StartUp project.
I'm creating a new form in a different project and wanted to know if there is a proper way to set a specific form load order post debug start.
Is there a some kind of a configuration for that or some checkbox for that, or maybe I'm just asking a really trivial question with an obvious answer (which I didn't find on my own)?
I'm running this projects on Visual Studio Express 2015 Desktop.
Thank you for any suggestions.
Related
I have just switched from Java-development (where I used IntelliJ) to an old WinForms application in VB.net. I have decided to use Rider, since I really liked IntelliJ.
From what I understand Raider's WinForm designer does not yet support VB.net-WinForms.
So my question is if there is a plugin that supports WinForms designing in Raider (to avoid having to switch to VS and avoid using 2 different IDEs).
The Winforms designer from Rider does only support C# with WinForms under Windows. It has recently added support for other toolkits, maybe in a cross-platform manner.
The answer to your question is no: and I don't think they are going to include since there is probably not enough demand. You can still use Visual Studio for the designer and go back to Rider when that part is finished.
My personal advice is to avoid use any designer. WinForms is really easy to grasp, and there are tutorials out there that make the task even easier.
One possibility would therefore be to get rid of the designer files and manually modify the code. An important outcome is that the project will be then editable in any IDE, not only Visual Studio or others with compatible plugins.
I'm developing a small WinForms program for home use - I have no intentions to releasing it anywhere.
Running it on my development machine, where I have Visual Studio and .NET and whatever else installed, works but deploying it on my PC, where I might not have all those frameworks, doesn't. I'm using some library written in C++ so I'm assuming I'm going to need some version of Visual C++ Redistributable, but I'm not sure which? And I'm not sure if that would be all. So, how can I determine an application's software prerequisites?
I used Dependency Walker and I got a message IEHIMS.DLL - Error opening file. The system cannot find the file specified (2), but that's all I could make out; there is so much information I'm having trouble make sense of it all. Besides, according to a quick google, IESHIMS.DLL has something to do with Internet Explorer, so it shouldn't really matter.
Thanks in advance to anyone taking to the time to consider my question.
Kind regards
For framework you can set the prerequisites for your application by going to project properties -> Publish -> Prerequisites. So now, if the required framework is not installed on the deployment machine, the setup will prompt for an install.
Now, for other dlls you are using, copy those dlls to your bin folder of the project and add the files while creating setup. This will solve the problem.
I am creating a Coded UI test for our system which runs on Sharepoint 2010. Part of the test sequence is creating a site; Sharepoint's UI for creating sites runs on Silverlight. Therefore, I need to create a Coded UI test for a Silverlight component which is part of out-of-the-box Sharepoint rather then part of our application. When I try to record a test, I get the following message:
No Silverlight controls where detected. Verify that the application under test is built using Silverlight assemblies with a version of 4.0 or greater and that a reference to the Microsoft.VisualStudio.TestTools.UITest.Extension.SilverlightUIAutomationHelper.dll assembly has been added to the project. For more information, see http://go.microsoft.com/fwlink/?LinkId=204562
I have two questions:
1) How can I find out the Silverlight version which Sharepoint components are built against? If they are built against Silverlight version 3.5 or earlier - I suppose the problem is unresolvable?
2) Assuming the previous question is answered - how can I make Sharepoint's Silverlight components reference the SilverlightUIAutomationHelper.dll library? That seems problematic at best to me...
Silverlight version installed on the test machine is 4; Visual Studio Feature Pack 2 is installed.
Thanks.
You can't make SharePoint's Silverlight components reference the automation helper library unless you have the source code and can recompile them. So the answer to your first question doesn't really matter.
You could modify Sharepoint XAPs to simply add Microsoft.VisualStudio.TestTools.UITest.Extension.SilverlightUIAutomationHelper.dll in there. You don't really need the code itself to reference it, it just has to part of the package. The XAP file is just a zip file so you should be able to modify this.
You will have to find where Sharepoint is getting the XAPs from and change the source (obviously you don't want to do this in prod boxes and there's even a license restriction for the Automation dll that prevents you from do it). You could also write a Fiddler AutoResponder to modify the XAP file and add the dll before it gets to the browser. For an example of this have a look at this AutoResponder:
https://bitbucket.org/mamadero/hackingsilverlightdemo/src/2fecb7b59dec/FiddlerAutoResponder
I know that this is a very stupid question, but I have not been able to find a definitive Guide to creating a basic Installer for my windows forms application. I know we have to use Setup and Deployment Projects in VS2010 but have not been able to find any step by step guide for it.
If possible please guide me regarding the same.
Thanks
Many Winforms projects don't require an installer. Just copy the files in the Release folder, formally named "XCopy deployment". The walkthrough for a Setup and Deployment project is here.
I'm currently learning how to do setup projects as well.. I found a couple of sites that helped me to get off the ground and have a basic installer. I know the first link is from way back in 2005, but it still helped.
http://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/
http://www.eggheadcafe.com/tutorials/aspnet/dcc5ab62-b875-4852-9e34-8bc2794e4fb8/c--create-setup-project.aspx
We are using Visual Studio 2008 to develop a winforms application stored in Visual Source Safe 2005.
If one of our team members changes a *.Designer.cs file without changing the form's source file the change doesn't appear during a "Get" operation. However, if in Visual Studio you run a compare on the *.Designer.cs file the differences are displayed in the difference viewer.
FYI: We are using the default Microsoft Visual SourceSafe plug in for Visual Studio.
Any ideas why the "Get" operation will not detect changes in the *.Designer.cs files and suggest we pull down the latest version?
Thanks for your help!
Designer files are not intended for manual manipulation. One of the chief incentives for adding partial classes to the popular .Net languages was to segregate the designer-generated code from manual user code, in fact. Manual manipulation of repeatedly-generated code (in pretty much any environment, not just visual studio) is asking for headaches.
What changes are you making to the designer file, and why is it not possible to make those changes to the non-designer source file?
Edit:
Is the project in the IDE properly bound and connected to the source control database (via File->Source Control->Change Source Control)? It should automatically be checking out the designer files when changes are made in the designer view.
I would try doing a Get manually through VSS Explorer (i.e. not through Visual Studio) and see if it works. If not, check to see if the file is pinned to a previous version.
Woe unto you for having to use SourceSafe. At my last job, we used SourceSafe and had a myriad of problems with it. We switched over to Surround SCM and were really happy with it. I'd never heard of it before that job.
To answer your question, any time I ran into a problem like this with SS, I'd do a "forced get": in the options dialog when you get latest, tell SourceSafe to get the latest version from the server regardless of whether it thinks the file is up to date.
Edit: I think the issue is the VS200X plugin for VSS. If you have the VSS standalone application you should be able to do a forced get from there. I now remember having to do this so often that I stopped using the VS200X plugin.