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
iForm interface minimal requirements #8100
Comments
Hello @davidekarasek ... This topic is slated for attention on #5331, but we don't have an ETA on that work yet. I recommend you post your question to a support forum, such as Stack Overflow, or support chat, such as Gitter or Slack. I'll add your issue to #5331 so that your inquiry here can be taken into account when the topic is updated. |
Please point me to ANY solution that works NOW that observes a separation of concerns HTML5 client and ASP.Net CORE 2.1 API. Thank you. |
Beyond what I did with file uploads and the Razor Pages tutorial (https://docs.microsoft.com/aspnet/core/razor-pages/upload-files) that does include an example of using Your best bet is ask on a support forum, such as Stack Overflow. Believe me, we do want to see the existing File Uploads topic overhauled/re-written. It's an issue of priorities. We're a small team, and we're 🏃🏃🏃🏃🏃😅 with high priority issues at the moment. Take a look at the one I did for the RP tutorial app and see if that at least provides some generally helpful guidance for your scenario. The fundamental concepts described in that topic should apply broadly to file uploads. However, file uploads is definitely a devil's-in-the-details subject, and that topic outlines some rather specific specifications that might not match exactly what you're trying to do in your own app. Sorry I can't be more help. My compatriot doc authors monitor these, so they'll chime in if they can provide additional assistance. |
Thank you. What was the standard way of posting files in the API before this latest tech? |
For me, it would have been using the old FileUpload server control in a webforms app. I mostly worked in webforms/VB before moving to MVC/C# not too long before getting into ASP.NET 5 lol .... er .... I mean ASP.NET Core. 😄 Back in those days, I took full advantage of all the plug-n-play server controls and AjaxControlToolkit goodies that made it easy/fast to whip up apps. Since those don't exist for Core, that's not going to work. I speculate that some of the third parties, like Telerik, have a plug-n-play AJAX control that can be dropped into an app. I'm very confident that there are blog posts out there that discuss file uploads with Core apps. There wasn't anything on Razor Pages at the time I wrote that topic ☝️, but I would hazard guess that there are a few blogs out there that have broached the subject of file uploads for RP as well. This convo is monitored by the other doc authors; so if they have anything to add, they'll jump in. |
Thanks for the follow up. I’m saddened by the complexity of this when this
is a standard process that apps like FsceBook use in the web. To be blunt,
I really really don’t like Razor for many reasons, primarily because it
tightly couples UI and service layer, just like classic web forms in .Net.
I did finally find a clean API/no bound UI coding example where the API’s
iFormFile controller gets called from and returns a JSON result from/to a
javaScript handler, though I understand there are limits to doing this with
iFormFile as well as AJAX handling of multi-part form submits. I just need
to thoroughly understand what those limits are.
Another part of the puzzle is reducing file size on upload. People take
large size photos and want to upload these simply but on this site the
images need to be constrained to 72 pixels per inch and no bigger than what
can quickly display on any device in a phone viewport.
-David
On Fri, Aug 17, 2018 at 3:08 PM Luke Latham ***@***.***> wrote:
For me, it would have been using the old FileUpload server control in a
webforms app. I mostly worked in webforms/VB before moving to MVC/C# not
too long before getting into *ASP.NET <http://ASP.NET> 5* lol .... er
.... I mean *ASP.NET <http://ASP.NET> Core*. 😄
Back in those days, I took full advantage of all the plug-n-play server
controls and AjaxControlToolkit goodies that made it easy/fast to whip up
apps. Since those don't exist for Core, that's not going to work.
I speculate that some of the third parties, like Telerik, have a
plug-n-play AJAX control that can be dropped into an app. I'm very
confident that there are blog posts out there that discuss file uploads
with Core apps. There wasn't anything on Razor Pages at the time I wrote
that topic ☝️, but I would hazard guess that there are a few blogs out
there that have broached the subject of file uploads for RP as well.
This convo is monitored by the other doc authors; so if they have anything
to add, they'll jump in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8100 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGNQFQuyq9datFJwfIPpelRTUbzns5Xmks5uRxS5gaJpZM4V-hlx>
.
--
David Evan Karasek
davidekarasek@gmail.com
|
Thanks for contacting us. |
Thanks. We already implemented this.
…On Mon, Feb 25, 2019 at 4:44 PM Rick Anderson ***@***.***> wrote:
Thanks for contacting us.
We don’t have the resources to invest in this area, so we are closing the
issue. Should your request generate enough 👍 responses, we’ll reconsider.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8100 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGNQFY8hCS7uJURnZIc9_Ra-gG5U6_kRks5vRFlWgaJpZM4V-hlx>
.
--
David Evan Karasek
davidekarasek@gmail.com
|
What are the minimal assembly requirements for the iForm interface. When I attempted to use it via nuget install it dragged in tons of assembly dependencies that totally bloated our heretofore simple and effecient .Net Core API. Also what's needed is an example that includes an HTML5 test harness, preferably using jQuery AJAX.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: