I just recently update my Xamarin Studio on Mac to version 6. As I updated it and starts working on current project, It seems strange. Its showing red line below InitialiseComponent() of every class. Red line for every name of control which is declared in xaml file. Though it builds the app successfully. Lets say I declared Entry in xaml and named it as "username", in code behind I am not able to access any property of "username".
Can somebody tell why this is happening with me.
Related
When trying to open the form deisgn it says values cannot be null. (Parameter 'baseName'). I still can run the system without error. Dont know how to fix it and have to change some gui design. Help me its for my school tnx
I had this problem this morning and a few hours later I decided to just start over and copy the code from the old project to the new empty project. Everything is working in the new copy of the project. I copied from old to new by drag-n-drop. I copied all the UserControls before I copied anything that uses them, and built, then copied over the remaining things, and went through all the errors caused by the change in name of the top-level Namespace.
(All of the Namespace errors were in the .Designer.vb files. I have posted elsewhere "never edit those files by hand unless you know what you are doing." This case was one of the rare exceptions.)
I had the OP's problem that when I tried to open a Form in the designer, I got the message
Value cannot be null. (Parameter 'baseName')
It didn't matter if I tried to open the Form in Solution Explorer or by pressing Shift-F7 in the Form's code window. However, sometimes Shift-F7 resulted in a wait cursor followed by silence - no error message.
Like the OP, the project did run without errors (well, same bugs as before but you know what I mean).
Another symptom: If I launched VS and tried to open the Form designer before Intellisense was initialized, instead of the other error, the window that should show the layout of the Form showed this instead:
File path: full path of the file I was trying to open
Frame GUID: 2c01570-c72c-11d0-88c3-00ac0c9110049
Frame mode: VSFM_MdiChild
Error code: 0x80131500
There are no MDI containers in my project. It's a reference to VS 2019.
The same error occurred in every Form and UserControl in the project.
The same error occurred in any new Form or UserControl that I added to the project.
The error did NOT OCCUR in any and all other projects built in VS 2019 with a target of .Net 5.0
The error DID OCCUR with the same project on another machine running a clean install of a later version of VS 2019.
Attempts to Clean Solution or Clean Project failed, with a generic error message, it was something like "Clean Project failed."
Nothing about these problems appeared in any event logs.
Every time the problem happened, when I shut VS, one process was left running (per TM).
Here are some other things I did to try to suss it:
Ran a repair install on VS 2019 and reboot.
Opened each and every VS-generated file in another project and compared them line-for-line (most are text) against the corresponding files in the broken project. No data-independent differences.
Searched exhaustively with 3 search engines and many terms for someone else that posted about this error. This is the only post I found.
Deleted, renamed, or moved files that are automatically generated by VS, including some Json files, XMLs, and caches.
What I did not try:
Roll back the code to the most recent commit.
Uninstall VS 2019 completely, reboot, install VS 2019 as if an initial installation.
Just had the same experience. I took me a while before I got everything to work again, but the clue in my case was that I had added a new item to my project, and for some reason I had managed to delete the file name in the process so the only thing left was 3 new files with only the extensions .resx, .cs and .Designer.cs
I quickly deleted the ".cs" file but forgot the rest.
Suddenly I was unable to open my main form in the designer - and the “Value cannot be null. (Parameter 'baseName')” started to appear. It was only affecting my main form.
I tried almost everything described above except the reinstalling part.
But then I deleted ".Designer.cs" and ".resx" from within visual studio (Solution Explorer), and then the problem went away.
I started getting this error after using a hack to support generics forms (e.g. MyForm). The designer generated a file:
MyForm.resx
which worked for design time (even with the form being generic) but crashed at runtime. My hack was to rename the .resx file:
MyForm`1.resx
However that is when the Designer stopped working. It stopped working for ALL forms/user controls in entire solution (not just the generic I was experimenting with). I assume there is some kind of process that crawls all the resx files whenever you open any Designer and that is the source of the Exception.
I was able to work around the issue by:
Renaming the resx back to its non generic title (i.e. MyForm.resx)
Restarting visual studio.
I am learning Xamarin Forms for Visual Studio 2015 and trying to create a simple Shared project using Xaml but I keep getting InitializeComponent does not exist (as well as any reference to Xaml controls in cs classes).
It is my understanding that in the latest versions of Xamarin, Xaml works in Shared Xamarin Forms Projects (and not only in PCL projects). I've tried running the latest betas that got released less than a month ago but still no luck.
Any advice is greatly appreciated.
Turns out I had to manually change the properties for all Xaml files like so:
Build Action: Embedded resource
Custom Tool: MSBuild:UpdateDesignTimeXaml
For some reason adding new Xaml forms files doesn't set these by default in VS2015 with latest Xamarin.
I had the same issue. And it turned out to be that fully qualified Class Name (x:Class attribute in the main node) in the XAML file must match exactly the xaml.cs file's name. I corrected the namespace casing and it worked!!
This happens when your XAML markup is invalid. There is a background compilation task that parses the XAML file and generates a code file (this is normally hidden from the developer) which declares those control references. If your XAML is not valid then this task will fail silently, and your first hints are the symptoms you describe.
Comment out the contents of your XAML file using standard XML comment syntax (wrap it with <!-- and -->), then rebuild your project to clear out all of the errors. You may also need to comment out some code in your .cs files temporarily to get it to build. Once you get it building, then you can go back and start uncommenting your XAML until you find the part that was breaking it.
Try it:
Open the Package Manager Console, put the follow line:
update-package -project your_pcl_project_name -reinstall
Similar to this question, I'm having trouble with an old webforms project in vs2015. The code will compile and run without error.
If I enable a breakpoint and try to look at any value in a Quickwatch, I get the following error:
error BC32208: Project already has a reference to assembly
'projectname.resources'. A second reference to
'projectname.resources.dll' cannot be added.
Similarly, if I break into the code and hover the mouse over a variable name then I do not get a pop-up containing the variable's current value.
I also looked at this microsoft link to no avail.
Is there a workaround for webforms?
My project doesn't have any localized [culture-code].resx files.
There's no assembly tab in project properties.
Amber Zhang from Microsoft contacted me to inform me that this has been resolved in vs2015 update 2. Downloaded and verified today. Thanks Amber!
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 have a VB.Net 2008 project that use ActiveReports. The problem is that any control on the report does not list the control's Name in the Properties window. All other properties seem to be there, just not the Name. The only way to change the name is to go into the forms .vb and change the name with a search and replace (like Me.Label1 to Me.lblAmount). All other forms are fine, it's just the ActiveReports forms. This happened just recently and there didn't seem to be any sort of update/event that triggered it. Anyone else have this issue before?
Thanks in advance,
-J
It is suggested that you download and upgrade to the most recent available build/service pack of the version of ActiveReports you are working with. And thereafter you should not face an issues.
The latest service packs can be downloaded from the following links :
AR3 : http://www.datadynamics.com/forums/121331/ShowPost.aspx
AR6 : http://www.datadynamics.com/forums/83/ShowForum.aspx
AR7 : http://our.componentone.com/groups/topic/activereports-7-service-pack-1-maintenance-release-now-available-2/
After the download, make sure that all of the dll’s of the upgraded version are present in the GAC. Also check that there isn't any dll of the previous version is present in GAC. After that remove all the ActiveReports references and then re-add the latest dll(s) in your project. Re-build the whole solution. You may also try creating a new project and check whether the name property appears.
Regards,
Mohita