I'm having to work in a vb.net project and I have to add new textfields and labels to a form. But when I change the layout of the form in Visual Studio the form looks fine, but after compilation and moving to a testserver the form all gets jumbled together and label/textfields are all over the place, and some are missing.
Why does this happens and how can I fix it? I think it could have something to do with form languages but I'm not sure. Since on test server there is a way to change the language from the app between dutch and french.
Was able to fix the the issue by compiling the code in visual studio 2010 instead of 2017. Thought i would give it a try since the application was initially developed in VS 2010 and it worked.
Related
When i'm typing code, the intellisense comes up to predict code, but before i can choose something in the list, its already gone. I know that you can use crtl+spacebar to bring it back up. But it's pretty annoying.
Does someone knows how to fix this?
(I'm using visual studio 17.3.1 (.Net - C#))
It is likely that this problem is caused by vs extension. You can try to disable the extensions and try again. If it doesn't work you can choose to reinstall Visual Studio.
The Reporting template seems missing in VS2017 (I am using Visual Basic). Any way to get it back?
I have already tried installing SQL Server Data tools and the rdlc extension from the marketplace, but it still doesn't show up.
The template is available in the Add New Item window. Select Visual C# and then look for the Report and Report Wizard templates. These templates are only visible under Visual C#, not under any subitem.
Try updating ReportViewer to version 14.0.0.0 and installing Microsoft.RdlcDesigner. This worked for me for Visual C# and then just like J.Bunch said there is no sub item Reporting like there was before so you just scroll down thorough all items. Also try this although the example is for C# I think it should at least help you with VB.Net as well. Hope it helps.
Currently I am using Visual Basic 2008 (.NET Framework 2.0) to create a program. However, when I add or select controls such as panels, group boxes, etc. I get error messages. For example, when I try to add a panel control I get the following message,
After clicking OK button, the panel control is added but the following happens to the panel control,
Yet I can still add other controls inside it. When I save and re-open the project, it shows the normal panel control. But when I select the panel control it does as shown in the second image again.
I tried this in Visual Basic 2008, 2010, 2012 and 2013. Same thing. I have full administrator access to the computer.
What is the reason for this and how to fix it?
I re-installed Windows and then Visual Studio 2008. The error did not occur after that. But when I updated the computer via Windows Update, the error came back.
Try creating a new project, then copy and paste code from the old project. You may or may not have to recreate the forms in the designer. Also, make sure you have System, System.Core, System.Drawing, and System.Windows.Forms included as references for the project.
The error was due to a Windows Update. Because it does not show any errors on non-updated Windows 7. The error only appears after updating Windows 7
It was difficult to find which update was the reason for the issue. The solution was to install Windows 7 and Visual Studio and never update it. This way, it seems to fix the issue and it does not show the errors anymore.
Reference: https://social.msdn.microsoft.com/Forums/vstudio/en-US/76790023-4d01-43a5-b901-65ad93a5183d/visual-studio-visual-basic-protected-memory-error?forum=visualstudiogeneral&prof=required
I've recently upgraded my project to Visual Basic 2008 and I'm getting the following errors which I cannot identify, I hope someone can help:
AxThreed.AxSSCommand is not defined
AxActiveInput.AxSSDropDownEdit is not defined
AxPVTEXT3DLib.AxPVText3D is not defined
Any idea what this is and how to fix it?
It looks these are references to 3rd Party ActiveX controls. ActiveThreed, Protoview Date Control, etc
You may need to Add/Re-Add the relevant control to your project. Right click on the toolbox so select the items to want to use. If you don't see them in the list to may need to register/re-register them on that machine
Have a look at this page for more info: http://msdn.microsoft.com/en-us/library/ms973200.aspx
Number 3 here seems to indicate how to fix the problem... I believe some of your controls are not loading.
We've recently upgraded from VS2008 to VS2010. The conversion of our vb.net Windows Forms app went well, but we're now having big problems with the forms designer.
Pretty much any change to the layout of a form (sometimes just a solution rebuild) will work once, but on recompile, the IDE designer refuses to display the form, the error message being a null-reference exception (with no details as to what).
Closing and restarting VS2010 will cure it, but only for one compile cycle - and it's obviously not practical to close and reopen every time. Closing and reopening the form does not fix it.
We had these very occasionally before, if there was something wrong in the form's load event, or more rarely for random reasons, but since VS2008 SP1 this was never serious.
Whereas now with VS2010, it's now every form, every compile.
It's completely unworkable, and we've had to revert to VS2008 for winforms dev.
Any suggestions would be greatly appreciated..
You can debug design mode:
In project properties, in the debugger tab, set the name of the executable to devenv.exe.
Run/debug the project: this launches a 2nd copy of Visual Studio
Use the 2nd (being debugged) copy Visual Studio to open the form in design mode
You may find more detailed information on the 'net, by Googling for 'debug design mode'.
Is your project Targets to .Net Framework 4 Client Profile or .Net Framework 4 ?
If you are not intentionally targeting to .Net Framework 4 Client Profile then change it to .Net Framework 4 you have a fair enough chance.
If, that was not helpful. Please do the above procedure as ChrisW said. That is the last option.
we faced the same problem. The reason ist, that the Handles statements are not converted
according the control name, but in capital letters.
However the controls themselves still contians the original correct name in lower case
or mixed. They also do this way in the designer.vb code.
You have to correct alle handles in the .vb code to match the name in the designer.vb code
of the same form.
A (fast) workaround is as follow.
a) Load the defective project.
b) Try to open a form
c) Press F7 to open the code
d) Replace all Handles to 'handles (search and replace, it works only form by form this way)
e) start a build
f) replace all 'handles to Handles
g) now the form should open
Unfortunately this works only form by form as VS 2010 'chockes'
loading too many forms at a time.
We are not taking any responsibility for the functionality not for eventual damage of your code using this suggestion!