I'm trying to add a Splash Screen to my form, but I'm getting the error -
'Application' is not a member of 'My'.
I've done some research and came across two possible solutions, but neither of them have worked for me.
Splash Screen Error "'Application' is not a member of 'My'." The answer here suggests ticking the 'Enable Application Framework' option in the Project settings, but that option is greyed out.
The 'My' Namespace in a VB.NET Application is Missing Members. This answer suggests that I need to add a Reference to the Project in the Project settings, but doing this does not fix the error.
Can anyone please suggest what I can do to solve this problem? Thanks.
That's a known issue for me. Open .vbproj file and change where it says
<MyType>Empty</MyType>
to
<MyType>WindowsForm</MyType>
We tried the suggestion above but it did not work for us with a Class Library in Visual Studio 2013.
After investigating another project that worked, we found that changing to using "Windows" instead of "WindowsForm" enabled that functionality
<MyType>Windows</MyType>
I recently ran into this issue as well. The solution in my case was that I had created a .NET Core app, rather than a .NET Framework app.
Copied my code into a new Framework app and it worked just fine.
Related
I installed recently the Xamarin platform and i created a default Xamarin.Forms Shared project using VS2015 and under the Droid project References i get a yellowish icon on System.ObjectModel library as you can see...
The weird thing is that in the beginning everything compiles but when i add a Cross-Platform -> Forms Xaml Page the compiler throws error on the InitializeComponent() method call.
I tried to manually reference System.ObjectModel.dll from the path C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades without any luck. When i right-click on the properties i get this
but in the file system properties everything seems to be correct.
All the above are with the default options.
Does this happen to you or it's just me? (i tested it in two computers)
If you have any questions i will update the post after this message...
Welcome to Xamarin! It's like tap dancing your way through a field of land mines. But XAML is awesome. Here is what worked for me: update your nuget of xamarin forms, do clean build, see the error/warning, restart visual studio, do a clean, restart visual studio again, do a build, spin your chair around 3 times counter-clockwise, and voila, the error is gone. It's like magic! No need to manually much around with dlls, it will just work.
Try to delete the contain of bin folder in PCL project and android project. and clean the solution try it again.
reference: http://xamarin103.rssing.com/browser.php?indx=50717177&item=8379
user: PubuduGayan, The second option that He suggested.
I hade same problem. Adding reference from C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.2\Facades... didn't work me.
What worked for me was to change (Tools/Options/Project and Solutions->Build and Run) Verbosity from normal to minimal, even if system.objectmodel reference-warning is still there.
Maybe this will work for developers too who are facing same problem
I faced the same problem. Deleting the reference helped in resolving the warning since System.ObjectModel was not used at all.
I am generating a WCF proxy using add web referance in Xamarin Studio
yet genrated proxy create the following error:
The type or namespace name IExtensibleDataObject' does not exist in the namespaceSystem.Runtime.Serialization'. Are you missing an assembly reference? (CS0234) (infra)
I am using mono4.0.5
Can anybody help me solve this problem that gave me many sleepless nights.
PS: I tried to skip proxy generation to using slsvcutil.exe code generation
but the same error keeps happening
Right click on you project and select Edit references. Look for System.Runtime.Serialization and select it.
If you already set the reference of System.Runtime.Serailization and error is still persist then try following regular steps..
clean solution and rebuild solution
restart visual studio
I found a solution for your problem. The problem is Xamarin Portable Targets. The targets must not contain any Windows targets selected. After changing this as in the image below it will not give you any compile time errors for System.Runtime.Serialization.
I found that after reading this https://developer.xamarin.com/guides/android/under_the_hood/assemblies/
The System.Runtime.Serialization.dll is for the Silverlight package and when selecting windows targets it might be removing these dlls/code not supported in windows platform from the portable libraries.
Recently Edit and Continue with VB.net has been kinda flaky.
In one project in particular. It was working as expected the last time I touched this project.
Recently when I pause the project while the winform message pump is running, I get a message saying no code is running. When I go back to my class file (in the same project, not external) I cannot make any changes - typing does nothing in the editor.
I have another class which is part of this solution, it has no entry point but I thought I would remind VS which was the startup project. This made edit and continue seem to work. I could make changes in the code, but when I continued the old version of the code was what was actually running. It's as if I am in an external class.
I just noticed something else, when you first start the project, edit and continue seems to work fine. After you continue, if you break the code again, it stops working.
I never had edit and continue problems at all with VS2012.
VS was hanging and crashing a lot yesterday so I rebooted my computer. That did not help this problem. I also installed SP1 and that did not fix anything.
I tried compiling to X86 and Any CPU.
Is there a setting I am missing? How can I get this working?
Thanks,
Brad
I tried a few more things based on some suggestion in other forums.
I repaired VS, I reinstalled VS, I tried to restore my default settings. None worked. I tried a simple project to duplicate the issue that I could share to get feedback. I could not get it to not work.
So assuming then the problem was with my project and not VS I made a new project and brought over my forms, modules and classes from project with the problem. I added my references and... edit and continue now works! The only things I changed from the default project were: Target CPU: x86, and Target Framework: .Net Framework 4
I still do not know if there was some corruption or it was a bad setting. This project was originally ported from VB6 many years ago and has been through a few VS upgrades as well.
for some reason I am getting an error "cannot read config file" when trying to set the SetExpressCheckout, I have copied across the web config settings, but for some reason I cannot read them, the error isn't very helpful other than what I have mentioned.
I am using mvc4, and to be honest I have had a problem reading the web.config in the past..
any suggestions would be much appreciated.
Just looked at this... thought it might help someone. Looked at the Inner Exception, saw it was looking for the Log4Net dll... so I gave it to the app and hey ho. It worked.
I had a similar problem and ended up getting both the core and merchant sdk source from GitHub. Change the SpecificVersion=True to False for the log4net reference in the core sdk and re-build it. I also re-targeted both for .net 4.0 so I re-built the merchant sdk with a reference to the new core sdk. Import both of these new dll's to your main project and you should be good to go. I had to change the config in 1 place for the section handler.
<section name="paypal" type="PayPal.Manager.SDKConfigHandler, PayPalCoreSDK"/>
since the Assembly name does not have the underscores if built from source (vs downloaded or added via NuGet).
A bit of explanation:
I was already using log4net version 1.11 before adding the sdk. The sdk was looking specifically for version 1.10. these 2 versions have a different public key, so 'simple' binding redirection won't work. If you have a reference to a different version of log4net (for example using ninject logging extensions requires min version 2.11 so these 2 ninject and the paypal sdk, are incompatible off the shelf).
so the root of the problem was actually caused by the dll version issues but manifested as a Configuration exception. check the inner exceptions and see what you get.
ok, just a quick update, I think it must be something to do with MVC, I have created a new empty asp project, copied the sdk config details across, created the same function call as I have in my mvc code, and called it from a simple asp button... and it works ??
does anyone have any ideas why I am getting an error in an mvc4 project, and not in a simple asp project ??
any help or ideas would be much appreciated.
I've post this question on MSDN (http://social.msdn.microsoft.com/Forums/en-US/winappswithhtml5/thread/9da1b0e4-6a03-41b2-b68e-6fefb4729c52). If it is considered as duplicated question, please remind me to delete it. Thanks.
I am using VS2012 pro on Win8 Pro. I encountered an issue and needs your help:
Let me simplify the scenario: Metro App (JavaScript) calls DLL1(a Windows Runtime Component), and DLL1 calls DLL2(a MFC DLL).
After I created a MFC DLL, then from "Configuration Properties", I changed the "use of MFC" as "Use Standard Windows Libraries", and changed "Windows Store App Support" as "Yes". But My Metro App always said that "0x8007007e - JavaScript runtime error: The specified module could not be found." After debugging, I found that the error is caused by DLL2. But I don't know why it is caused.
Does anybody know anything about this? Or would you please give me some hint?
Thank you all.
I think it is necessary to add my solution: I must manually add the external dependent dll (not the system dll but built by yourself or others) into my js project by "added as link". Thus the issue could be resolved. If any encounter the same issue, please write to me and let's discuss it. Thanks.