Тёмный

WCF using C#: Using metadata exchange 

Jesse Dietrichson
Подписаться 27 тыс.
Просмотров 16 тыс.
50% 1

*NEW*
Follow us on Twitter
/ jdprogramming
WCF using C#: Using metadata exchange
If you would like to see specific videos, please feel free to ask.
If you found this video useful, please like and subscribe!

Опубликовано:

 

23 июл 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 14   
@MrKirankoyelada
@MrKirankoyelada 7 лет назад
Thanks Nice Explanation
@majordan9747
@majordan9747 4 года назад
thanks a lot. look to your sharing more programming experience.
@ANIMELRYUZAKI
@ANIMELRYUZAKI 7 лет назад
do you know how to get the metadata from a song(can be a file mp3) in c?
@parkromanson906
@parkromanson906 9 лет назад
It doesn't work , can you please share your code.
@BDMSydney
@BDMSydney 10 лет назад
Hi Jesse, Many thanks for your videos, there are very practical and useful. I've done everything exactly same as your video but when I want to add service refrence to client I get this error : There was an error downloading 'localhost:9999/mex/_vti_bin/ListData.svc/$metadata'. The request failed with HTTP status 400: Bad Request. Metadata contains a reference that cannot be resolved: 'localhost:9999/mex'. Metadata contains a reference that cannot be resolved: 'localhost:9999/mex'. If the service is defined in the current solution, try building the solution and adding the service reference again. I've checked my config file it's exactly same as yours, my service and VS are running as administrator.
@PATHAKROHIT08
@PATHAKROHIT08 10 лет назад
Have you set httpGetEnabled=true ?
@welingtonws
@welingtonws 8 лет назад
It does not work. After trying to add service reference I get this error: There was an error downloading 'localhost:9999/mex/_vti_bin/ListData.svc/$metadata'. The request failed with HTTP status 400: Bad Request. Attribute 'contract' is required on element 'endpoint'. If the service is defined in the current solution, try building the solution and adding the service reference again.
@welingtonws
@welingtonws 8 лет назад
+welingtonws Just found the solution.... I had to create a base address and reconfig Mex and ServiceProduct endpoints do agree with that base address (replacing to /mex for ex, instead of the complete address). In the serviceMetadata behavior I set HttpGetEnabled to True and HttpGetUrl to the absolute address (localhost:9999/mex). On my client app.config, I had to create the attribute contract on endpoint node like this: contract="*". Only then I could reference the service.
@steph8804
@steph8804 7 лет назад
can you show your code...your description is pretty vague...
@steph8804
@steph8804 7 лет назад
same as others...it doesn't work as its shown in the video...have tried what others have suggested and its still not working properly UPDATE: OK, I have it working properly exactly as he has it setup...the key was to listen to what he said before running it--he said you had to run it "Not in Debug Mode" which means you have to use CTRL+F5 instead of F5. Then while its still open you go and right click on ProductsClient and then Add Service Reference...type in localhost:9999/mex and it works exactly as shown.