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

Unable to resolve type: React.IReactEnvironment #412

Closed
fm-gawdeprasad opened this issue May 29, 2017 · 3 comments
Closed

Unable to resolve type: React.IReactEnvironment #412

fm-gawdeprasad opened this issue May 29, 2017 · 3 comments

Comments

@fm-gawdeprasad
Copy link

Hi Team,

As per the instructions given on link1. I created a sample React.Net application in Visual Studio 2013. Then I opened it in VS2015 (I wanted to use MVC4 setup). But when I run the application I get error Unable to resolve type: React.IReactEnvironment.

I am sharing the zipped solution with this so that you can reproduce it easily. It can be accessed at link2

image

@fm-gawdeprasad
Copy link
Author

I worked on it further and figured out that ReactEnvironment will not be available when ReactConfig.Configure() is executing so I moved the statement to resolve IReactEnvironment within App_Start() of Gobal.asax and it is working fine on my local box (Windows 8 .Net 4.5.2 framework) but when I move it to the testing machine (Windows Server 2008 R2 .Net 4.5.2), it gives following exception

image

I checked it on Server 2012 and 2016 as well, where it works fine but only 2008 seems to have some issues which I am not able to figure out yet. Luckily all production servers are on Server 2016 but for testing I have disabled ReactJs.Net till I figure out the issue.

You can check my sample code at link1

Any direction where I can look into would be of great help.

@Taritsyn
Copy link
Contributor

@cw-gawdeprasad I recommend you to read the “MSIE” section of “Misconceptions about the JavaScript Engine Switcher version 2.X” discussion.

@fm-gawdeprasad
Copy link
Author

Thanks a lot @Taritsyn . I should have first read your article. IE is the culprit.

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

2 participants