Windows mobile client for ASMX Web Service - windows

I try make simple Windows mobile client for web service. The web method only add two integer. I add reference on proxy and System.Web.Service.
But it finish with this error :
The type 'System.Web.Services.Protocols.SoapHttpClientProtocol' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
But I add reference on System.Web.Service
I check, and in reference is add :
Assembly System.Web.Services
E:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Web.Services.dll
I use Visual Studio 2008, where is a problem ? I try first google, but I didn't find answer. Thank

Looks like you've added a reference to the 3.5 version of system.web.services.dll, but it's asking for version 2.0. Try referencing the file at:
E:\Program Files\Microsoft.NET\SDK\CompactFramework\ v2.0 \WindowsCE\System.Web.Services.dll

Related

missing assemblies Xamarin when creating new project [duplicate]

Im learning Xamarin, when I try to create a project and build it, it gives me this error:
The "Xamarin.Forms.Build.Tasks.GetTasksAbi" task could not be loaded
from the assembly ,
C:\Users\XXXX.nuget\packages\xamarin.forms\3.0.0.482510\build\netstandard2.0\Xamarin.Forms.Build.Tasks.dll.
Could not load file or assembly 'netstandard, Version=2.0.0.0,
Culture=neutral
I really dont know how to solve it. I installed Visual Studio with Xamarin found at this link
This is the cause:
Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral
Starting with Xamarin-Forms 3, XF has moved to .Net Standard 2.0, so you need to create a library against .net standard 2.0.
Thanks for all the suggestions. I just updated Windows 10 and it worked. I had and old Windows build so I guess it was related to my Windows being outdated.

Is it possible to reference different NuGet package versions in a Visual Studio solution?

We are a team composed of 7 members and we want to create a Cloud Application (Windows Azure) with Visual Studio. Our application is hosted on GitHub so we have choose to use NuGet packages to keep our repository light as possible.
However two different projects in our Visual Studio solution need reference either Newtonsoft.Json version 4.0.2 or Newtonsoft.Json version 4.5.11.
We have tried to reference the right version for each project but we get this errors on build:
The type 'Newtonsoft.Json.Linq.JObject' is defined in an assembly that is not referenced. You must add a reference to assembly 'Newtonsoft.Json, Version=4.0.2.0, Culture=neutral, PublicKeyToken=null'.
Cannot implicitly convert type 'Newtonsoft.Json.Linq.JObject' to 'Newtonsoft.Json.Linq.JObject'
The second error suggests that there are conflicts between the two versions even if no project in our solution references the two version at the same time.
Do you have any idea to solve this problem?
Thanks.
PS: Here are the most relevant information we have found about this issue.
http://docs.nuget.org/docs/reference/known-issues
https://stackoverflow.com/search?q=NuGet+multi+packages+version
After a while... Know that we have rewrite the piece of code which use the old reference to Newtonsoft.Json version 4.0.2.
Thanks.

Error adding webpart

I'm developing a webpart in Sharepoint 2013 using VS2012. In this webpart I'm using a custom dll that I created. The library framework is 4.0 and the visual webpart framework is 4.5.
The problem is when I'm adding the webpart in sharepoint page, the following error appeared:
Could not load file or assembly 'RulesDll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d2371e81bc184aa5' or one of its dependencies. The system cannot find the file specified
Searching in google I found a lot of solutions to resolve this problem
Adding library to GAC using two methods.
(1) gacutil -i RulesDll.dll
(2) Using package ---> Advanced options in the solution explorer in VS2012
When I running gacutil -l RulesDll in VS command prompt everything sames to work:
Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.17929
Copyright (c) Microsoft Corporation. All rights reserved.
The Global Assembly Cache contains the following assemblies:
RulesDll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d2371e81bc184aa5, processorArchitecture=x86
Number of items = 1
So the library is in the GAC.
Adding the library to the save control in web.config
But nothing works. Does someone know why it's impossible to add my own webpart in a sharepoint page?
What's the error you get once your assembly is in GAC and you try to add the webpart on the page?
Check the web.config of your application and especially the SafeControls section, there should be a reference to your assembly.
http://technet.microsoft.com/en-us/library/cc261736.aspx
Finally found the error. All libraries must be deploy in x64

Missing reference while Converting VS2008 project to VS2010 project

When i converted a VS2008 project to 2010 it shows an error message
The type name 'IComponentConnector' could not be found in the namespace 'System.Windows.Markup'. This type has been forwarded to assembly 'System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Consider adding a reference to that assembly
and it was build when we add a reference System.Xaml. What would be the reason for need to add additional reference?
In .Net 3.5/3,0, IComponentConnector (namespace System.Windows.Markup) was part of WindowsBase.dll and it was moved in System.Xaml in .net 4.0 onwards.
It seems you are upgrading your project framework 3.5 to 4.0
The type was moved to the new assembly in .net 4?
You are changing you project to use .net 4 and it's telling you that you need this type from that assembly in .net 4.
if you target .net 3.5 you'll find you wont need to do this.
As a thumb rule, always add the namespace that is documented. The document says to use the namespace System.Windows.Markup. It worked in VS2008 probably because System.Xaml was internally using the namespace System.Windows.Markup.

AjaxControlToolkit.CalendarExtender and System.Web.Extentions version error

I have VS 2005, 2008 on my dev box.
New project from other developers who only have 2005 installed. When I build it I get error.
Error 1 Indirect reference is being made to assembly
System.Web.Extensions version 3.5.0.0, which contains
'AjaxControlToolkit.CalendarExtender'. This Project references a prior
version of System.Web.Extensions version 1.0.61025.0. To use
'AjaxControlToolkit.CalendarExtender', you must replace the reference
to System.Web.Extensions with version 3.5.0.0 or higher.
When I change the version of Web.Extentions to 3.5 I get another failure
Could not load file or assembly 'AjaxControlToolkit,
Version=1.0.20229.23876, Culture=neutral,
PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The
located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
Should I change the Public key for:
add assembly="System.Web.Extensions, Version=1.0.61025.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35"
to the newer one, or is this the wrong thing to do. the Server does NOT have 3.5 runtime.
TIA
If your server doesn't have the 3.5 runtime and you aren't able to install it, I suppose you must stick with the 1.0.61025.0 version of System.Web.Extensions.
I would guess that the problem you are encountering is because the AjaxControlToolkit dll that you are using was built with the 3.5 runtime. Thus, your project is referring both to the 1.0.6... version directly and to the 3.5 version through the AjaxControlToolkit reference, and getting confused. You might try downloading the toolkit source and building it from scratch, referencing the 1.0.61025.0 version of System.Web.Extensions. Then make sure to reference this toolkit instead of the default one.
http://ajaxcontroltoolkit.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=11121
Also, you might try making sure that all the references to the System.Web.Extensions DLL version number are consistent, both in your project's references and in the web.config file. Note that if you have a reference selected, you can toggle the "SpecificVersion" property to True in the Properties panel; presumably this makes .NET more picky as to which DLL version it chooses.

Resources