Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The type or namespace name 'IMetafield' could not be found #64

Closed
MartyIce opened this issue Jul 4, 2018 · 5 comments
Closed

The type or namespace name 'IMetafield' could not be found #64

MartyIce opened this issue Jul 4, 2018 · 5 comments

Comments

@MartyIce
Copy link

MartyIce commented Jul 4, 2018

Where is IMetafield (referenced by ChargifyConnect class) defined? I did a clean pull and am seeing the following error trying to build (in VS2017):

The type or namespace name 'IMetafield' could not be found (are you missing a using directive or an assembly reference?) ChargifyDotNet(netstandard2.0)

\chargify-dot-net\Source\ChargifyDotNet\ChargifyConnect.cs 215

@robfarmergt
Copy link

@MartyIce wondering if you were able to resolve this at all?

@Romeid
Copy link

Romeid commented Oct 24, 2018

When I pulled it down the other day I ran into this and after looking around it looks like it was pulled in during the issue fix for #61 - I couldn't find any references to it in the code in my quick search and a google search seems to lead to some sitefinity CMS thing? I dunno.

Since I couldn't find any reference to the code within the library itself, I just removed that method and everything built fine.

https://github.com/kfrancis/chargify-dot-net/search?q=GetMetafields&unscoped_q=GetMetafields

@robfarmergt
Copy link

That worked for me as well, thanks!

@Romeid
Copy link

Romeid commented Oct 24, 2018

No problem!

Some more searching and there does seem to be some metafields/metadata functionality related to subscriptions supported by the API: https://www.chargify.com/blog/metafields-and-metadata-api-endpoints/ So this might be the in progress (ie: incomplete) work on implementing that, i haven't looked at the code close enough to confirm this though.

@kfrancis
Copy link
Owner

Sorry everyone, this was related to some code that hadn't been checked in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants